Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.57763671875e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.24219775199890137s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6081950664520264s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007135868072509766s
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 8.821487426757812e-06s
INFO | --- Analysis for 0080-3626 took 8.219799041748047s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.458427429199219e-05s
Availability | VoID file availability check for 土地利用图 took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.23594999313354492s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020115375518798828s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.218650817871094e-05s
Believability | Calculation of trust value for 土地利用图 took 7.62939453125e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 3.043807029724121s
Availability | SPARQL endpoint availability check for 113322 took 4.267692565917969e-05s
Availability | VoID file availability check for 113322 took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for 113322 took 0.2377004623413086s
Reputation | Calculation of the PageRank for 113322 took 0.020241737365722656s
Interlinking | Calculation of Degree of Connection for 113322 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.956390380859375e-05s
Believability | Calculation of trust value for 113322 took 8.58306884765625e-06s
INFO | --- Analysis for 11 took 4.33864951133728s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.38690185546875e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.24269533157348633s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.647804260253906e-05s
Believability | Calculation of trust value for Korepetycje Buki took 7.867813110351562e-06s
INFO | --- Analysis for 12323 took 2.183349847793579s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.9034388065338135s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2516946792602539s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.012222290039062e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 6.9141387939453125e-06s
INFO | --- Analysis for 2000-us-census-rdf took 5.841287851333618s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.7500710487365723s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.24845242500305176s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.025631427764892578s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.001215219497680664s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 7.605552673339844e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 8.106231689453125e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 5.584779977798462s
Availability | SPARQL endpoint availability check for Open Data Web took 0.08491158485412598s
Availability | VoID file availability check for Open Data Web took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.24264883995056152s
Reputation | Calculation of the PageRank for Open Data Web took 0.026114702224731445s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.001180410385131836s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 5.626678466796875e-05s
Believability | Calculation of trust value for Open Data Web took 9.775161743164062e-06s
INFO | --- Analysis for _data.odw.tw took 2.3037376403808594s
Availability | SPARQL endpoint availability check for 土地利用 took 4.6253204345703125e-05s
Availability | VoID file availability check for 土地利用 took 0.0003829002380371094s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2399451732635498s
Reputation | Calculation of the PageRank for 土地利用 took 0.026237010955810547s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0012269020080566406s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 5.14984130859375e-05s
Believability | Calculation of trust value for 土地利用 took 9.059906005859375e-06s
INFO | --- Analysis for _data1.odw.tw took 2.147962808609009s
Availability | SPARQL endpoint availability check for 土地利用模型 took 6.365776062011719e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.24512529373168945s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.026372671127319336s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0012161731719970703s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 5.0067901611328125e-05s
Believability | Calculation of trust value for 土地利用模型 took 9.298324584960938e-06s
INFO | --- Analysis for _data2.odw.tw took 5.4955737590789795s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.3392181396484375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.23927021026611328s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021590232849121094s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.361701965332031e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.198883056640625e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.086778402328491s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 5.030632019042969e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.3170585632324219s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02109074592590332s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.9577484130859375e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 8.344650268554688e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 484.05140376091003s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.458427429199219e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.23600316047668457s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020093202590942383s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.9802322387695312e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 5.7220458984375e-06s
INFO | --- Analysis for A1 took 3.0338988304138184s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.1252086162567139s
Availability | VoID file availability check for SummerOlympics took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.23965048789978027s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.318092346191406e-05s
Believability | Calculation of trust value for SummerOlympics took 8.821487426757812e-06s
INFO | --- Analysis for abc took 5.610135793685913s
Availability | SPARQL endpoint availability check for Test_m took 4.649162292480469e-05s
Availability | VoID file availability check for Test_m took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Test_m took 0.2404162883758545s
Reputation | Calculation of the PageRank for Test_m took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for Test_m took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.0994415283203125e-05s
Believability | Calculation of trust value for Test_m took 7.867813110351562e-06s
INFO | --- Analysis for ABC took 2.1227307319641113s
Availability | SPARQL endpoint availability check for my intro took 4.410743713378906e-05s
Availability | VoID file availability check for my intro took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for my intro took 0.24446535110473633s
Reputation | Calculation of the PageRank for my intro took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for my intro took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for my intro took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for my intro took 3.075599670410156e-05s
Believability | Calculation of trust value for my intro took 7.62939453125e-06s
INFO | --- Analysis for abhay_intro took 2.587402105331421s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.1802356243133545s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.24665498733520508s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010347366333007812s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for abs-linked-data took 2.3755226135253906s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 4.601478576660156e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.23437809944152832s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.9087066650390625e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 7.62939453125e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.622317314147949s
Availability | SPARQL endpoint availability check for AcadOnto took 4.410743713378906e-05s
Availability | VoID file availability check for AcadOnto took 0.00034308433532714844s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.24161458015441895s
Reputation | Calculation of the PageRank for AcadOnto took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for AcadOnto took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.9802322387695312e-05s
Believability | Calculation of trust value for AcadOnto took 8.106231689453125e-06s
INFO | --- Analysis for acadonto took 4.049694776535034s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 10.021110773086548s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0012362003326416016s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.25895023345947266s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.027871370315551758s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0014028549194335938s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 6.699562072753906e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for acorn-sat took 36.38575482368469s
Availability | SPARQL endpoint availability check for Addgene took 8.440017700195312e-05s
Availability | VoID file availability check for Addgene took 0.0009379386901855469s
Completeness | Calculation of interlinking completeness for Addgene took 0.24834585189819336s
Reputation | Calculation of the PageRank for Addgene took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for Addgene took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.2438507080078125e-05s
Believability | Calculation of trust value for Addgene took 8.821487426757812e-06s
INFO | --- Analysis for addgene took 37.589091062545776s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.553794860839844e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.24812889099121094s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.608268737792969e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 5.9604644775390625e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 4.057062387466431s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.4622766971588135s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.24888038635253906s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020982980728149414s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.4345855712890625e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 6.4373016357421875e-06s
INFO | --- Analysis for aemet took 4.430312395095825s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.3392181396484375e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.2422013282775879s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.170967102050781e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 6.67572021484375e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.6839592456817627s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.038776397705078125s
Availability | VoID file availability check for AgriNepalData took 0.000213623046875s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.24630498886108398s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.390975952148438e-05s
Believability | Calculation of trust value for AgriNepalData took 6.198883056640625e-06s
INFO | --- Analysis for agrinepaldata took 2.3286101818084717s
Availability | SPARQL endpoint availability check for AGRIS took 262.45290327072144s
Availability | VoID file availability check for AGRIS took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for AGRIS took 0.2383716106414795s
Reputation | Calculation of the PageRank for AGRIS took 0.021463394165039062s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0011055469512939453s
Interlinking | Calculation of Clustering coefficient for AGRIS took 9.799003601074219e-05s
Believability | Calculation of trust value for AGRIS took 1.1205673217773438e-05s
INFO | --- Analysis for agris took 555.5263605117798s
Availability | SPARQL endpoint availability check for AGROVOC took 0.1473696231842041s
Availability | VoID file availability check for AGROVOC took 0.0005805492401123047s
Extra | Recovery of all triples for AGROVOC took 34.5459623336792s
Performance | Total latancy measurement for AGROVOC took 0.41068243980407715s
Amount of data | Number of triples check for AGROVOC took 30.074647903442383s
Interoperability | New terms check for AGROVOC took 3.928992986679077s
Versatility | Languages check for AGROVOC took 30.07627844810486s
Interpretability | Number of blank nodes check for AGROVOC took 30.07716417312622s
Interpretability | RDF structures check for AGROVOC took 0.0862588882446289s
Versatility | Serialization formats check for AGROVOC took 0.08088803291320801s
Availability | RDF dump link check for AGROVOC took 0.07668447494506836s
License | MR license check for AGROVOC took 0.08514213562011719s
License | HR license check for AGROVOC took 1.4028892517089844s
Amount of data | Number of property check for AGROVOC took 0.0811619758605957s
Understandability | Number of label check for AGROVOC took 30.07595205307007s
Understandability | URI regex check for AGROVOC took 0.34006166458129883s
Understandability | Vocabs check for AGROVOC took 0.08350753784179688s
Verifiability | Authors check for AGROVOC took 0.0806887149810791s
Verifiability | Publishers check for AGROVOC took 0.08590149879455566s
Performance | Throughput check for AGROVOC took 10.362287998199463s
Amount of data | Check the number of entities for AGROVOC took 6.198883056640625e-05s
Verifiability | Contribs. check for AGROVOC took 0.1701641082763672s
Interlinking | sameAs chians check for AGROVOC took 0.17238354682922363s
Interlinking | skos check for AGROVOC took 0.17126798629760742s
Interlinking | skos check for AGROVOC took 0.17248940467834473s
Timeliness | dataset update frequency check for AGROVOC took 0.17178726196289062s
Currency | Creation date check for AGROVOC took 0.24823451042175293s
Currency | Modification date check for AGROVOC took 0.1535320281982422s
Rep.Conc. | URIs length for AGROVOC took 51.33071780204773s
Interoperability | New vocabularies check for AGROVOC took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08279800415039062s
Accuracy | Check Empty annotation labels for AGROVOC took 21.71812891960144s
Accuracy | Check White space in annotation for AGROVOC took 2.6631882190704346s
Consistency | Disjoint class check for AGROVOC took 0.07784032821655273s
Consistency | Check Misplaced properties for AGROVOC took 23.80412220954895s
Consistency | Check Ontology hijacking for AGROVOC took 30.07820153236389s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 22.757989645004272s
Conciseness | Check Extensional conciseness for AGROVOC took 0.00017690658569335938s
Conciseness | Check Intensional conciseness for AGROVOC took 0.10435748100280762s
Security | Sign check for AGROVOC took 0.09619593620300293s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.31812596321105957s
Reputation | Calculation of the PageRank for AGROVOC took 0.021018505096435547s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011229515075683594s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.9073486328125e-06s
Believability | Calculation of trust value for AGROVOC took 8.821487426757812e-06s
INFO | --- Analysis for agrovoc took 402.41914987564087s
Availability | SPARQL endpoint availability check for AGROVOC took 4.1484832763671875e-05s
Availability | VoID file availability check for AGROVOC took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.25034213066101074s
Reputation | Calculation of the PageRank for AGROVOC took 0.020174741744995117s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.8650970458984375e-05s
Believability | Calculation of trust value for AGROVOC took 7.62939453125e-06s
INFO | --- Analysis for agrovoc-skos took 3.1557819843292236s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 4.506111145019531e-05s
Availability | VoID file availability check for Analytics India Magazine took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.2476954460144043s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.0994415283203125e-05s
Believability | Calculation of trust value for Analytics India Magazine took 7.3909759521484375e-06s
INFO | --- Analysis for AIM took 3.581738233566284s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.458427429199219e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.24795150756835938s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.2901763916015625e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 7.152557373046875e-06s
INFO | --- Analysis for AISHE took 2.17617130279541s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.1961669921875e-05s
Availability | VoID file availability check for  equipment ontology took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.2460341453552246s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02001023292541504s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for  equipment ontology took 7.62939453125e-06s
INFO | --- Analysis for akash took 2.6193041801452637s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.649162292480469e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.24616408348083496s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.170967102050781e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 8.58306884765625e-06s
INFO | --- Analysis for aksworg took 2.678908586502075s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.172325134277344e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.2471470832824707s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.0517578125e-05s
Believability | Calculation of trust value for AlchemyAPI took 8.106231689453125e-06s
INFO | --- Analysis for alchemyapi took 2.697892904281616s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.220008850097656e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.2484264373779297s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.075599670410156e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 7.62939453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.6778199672698975s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.0845131874084473s
Availability | VoID file availability check for aliada-scanbit-net took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.24280333518981934s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011587142944335938s
Believability | Calculation of trust value for aliada-scanbit-net took 7.867813110351562e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.363391637802124s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.1484832763671875e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.23950839042663574s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02007889747619629s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.075599670410156e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 7.867813110351562e-06s
INFO | --- Analysis for allen-brain-atlas took 2.6689465045928955s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.349606990814209s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0007059574127197266s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 548.6365106105804s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.682286262512207s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 2.800689458847046s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.5955188274383545s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.10352396965027s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 8.44871711730957s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8554179668426514s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7440330982208252s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6525189876556396s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5563468933105469s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.56675124168396s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 39.74559283256531s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5908892154693604s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7731904983520508s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1074488162994385s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5593938827514648s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.5864889621734619s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5571057796478271s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.65011739730835s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 8.344650268554688e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.6544051170349121s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5657134056091309s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5669918060302734s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.539764404296875s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5583329200744629s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.1754140853881836s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1437909603118896s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 194.92409372329712s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5558936595916748s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6546792984008789s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6017904281616211s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 148.35266280174255s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.034269094467163s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.6333799362182617s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6055099964141846s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 11.394229650497437s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.810384035110474s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 128.6423144340515s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3704619407653809s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 12.226211786270142s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7524843215942383s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8271265029907227s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5634279251098633s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12581.731016635895s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.229874610900879s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02153778076171875s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.845329284667969e-05s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 7.62939453125e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14117.063883304596s
Availability | SPARQL endpoint availability check for Alojamientos took 4.0531158447265625e-05s
Availability | VoID file availability check for Alojamientos took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.6823763847351074s
Reputation | Calculation of the PageRank for Alojamientos took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0008649826049804688s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.409385681152344e-05s
Believability | Calculation of trust value for Alojamientos took 7.3909759521484375e-06s
INFO | --- Analysis for alojamientos-zaragoza took 3.5735628604888916s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.36429333686828613s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.25136899948120117s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020281314849853516s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.838539123535156e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 9.059906005859375e-06s
INFO | --- Analysis for alpino-rdf took 4.34862756729126s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.3392181396484375e-05s
Availability | VoID file availability check for AAT-atawil took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2484755516052246s
Reputation | Calculation of the PageRank for AAT-atawil took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.409385681152344e-05s
Believability | Calculation of trust value for AAT-atawil took 6.9141387939453125e-06s
INFO | --- Analysis for Altawil took 2.2104732990264893s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.1961669921875e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.24916982650756836s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.170967102050781e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 8.58306884765625e-06s
INFO | --- Analysis for am-collections-online took 3.621584415435791s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.6253204345703125e-05s
Availability | VoID file availability check for Amer Nejma took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.2500581741333008s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.3855438232421875e-05s
Believability | Calculation of trust value for Amer Nejma took 8.821487426757812e-06s
INFO | --- Analysis for Amer_Nejma took 2.2147934436798096s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 7.557868957519531e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.24767017364501953s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020096778869628906s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 7.152557373046875e-06s
INFO | --- Analysis for amon took 2.671614170074463s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.5533437728881836s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.24995636940002441s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020329952239990234s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.1552734375e-05s
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.418426990509033s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 3.981590270996094e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.24750328063964844s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.0040740966796875e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 6.4373016357421875e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.681182622909546s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.029273986816406e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.24729585647583008s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020143747329711914s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 2.86102294921875e-05s
Believability | Calculation of trust value for Animal Diversity Web took 5.7220458984375e-06s
INFO | --- Analysis for animal-diversity-web took 2.681567907333374s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for Anime Dataset took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.24326658248901367s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020018339157104492s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Anime Dataset took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Anime Dataset took 6.67572021484375e-06s
INFO | --- Analysis for Anime took 3.7326745986938477s
Availability | SPARQL endpoint availability check for ANNO took 4.220008850097656e-05s
Availability | VoID file availability check for ANNO took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for ANNO took 0.2451038360595703s
Reputation | Calculation of the PageRank for ANNO took 0.021146774291992188s
Interlinking | Calculation of Degree of Connection for ANNO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.647804260253906e-05s
Believability | Calculation of trust value for ANNO took 7.867813110351562e-06s
INFO | --- Analysis for anno took 7.672415256500244s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.076957702636719e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.24668598175048828s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.700920104980469e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 6.67572021484375e-06s
INFO | --- Analysis for AntiqueCarsCollection took 4.358310699462891s
Availability | SPARQL endpoint availability check for apache took 4.1484832763671875e-05s
Availability | VoID file availability check for apache took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for apache took 0.24614286422729492s
Reputation | Calculation of the PageRank for apache took 0.020119428634643555s
Interlinking | Calculation of Degree of Connection for apache took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for apache took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for apache took 5.221366882324219e-05s
Believability | Calculation of trust value for apache took 6.4373016357421875e-06s
INFO | --- Analysis for apache took 3.850884437561035s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.24776911735534668s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF took 3.266334533691406e-05s
INFO | --- Analysis for apertium-rdf took 4.453551769256592s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.00033164024353027344s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2351086139678955s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.02117133140563965s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0009098052978515625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.101507186889648s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.2540872097015381s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 5.9604644775390625e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.152544736862183s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2565760612487793s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 5.173683166503906e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 5.4836273193359375e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.223576307296753s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.25455355644226074s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02024054527282715s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 9.5367431640625e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.183617353439331s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0003790855407714844s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.24294257164001465s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.190402269363403s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.24532723426818848s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02019977569580078s
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.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 5.4836273193359375e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.259788990020752s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.24916577339172363s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020110130310058594s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.124641418457031e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.199541330337524s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2512321472167969s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020047903060913086s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.207743167877197s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0007767677307128906s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2512633800506592s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.0201413631439209s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 5.4836273193359375e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.207561492919922s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 6.031990051269531e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.24919843673706055s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020240068435668945s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.2174036502838135s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.100799560546875e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.2518751621246338s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020052433013916016s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.124641418457031e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.570574522018433s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.124641418457031e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0011892318725585938s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.25284767150878906s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020201921463012695s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.100799560546875e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.190526008605957s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.25118231773376465s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02021002769470215s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.220461845397949s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.25072574615478516s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020247936248779297s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.219539642333984s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.24467182159423828s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020073890686035156s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.161059617996216s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 7.557868957519531e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2567119598388672s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02024245262145996s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 5.193513631820679s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2481520175933838s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.177143812179565s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.24973082542419434s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 5.245208740234375e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.193916320800781s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2486872673034668s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.207697868347168s
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.0006091594696044922s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2460165023803711s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.1467835903167725s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.25746583938598633s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.254394769668579s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.3584022521972656s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020212173461914062s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.116087198257446s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.6129450798034668s
Availability | VoID file availability check for AragoDBPedia took 0.0006549358367919922s
Extra | Recovery of all triples for AragoDBPedia took 2.900254964828491s
Performance | Total latancy measurement for AragoDBPedia took 1.9118859767913818s
Amount of data | Number of triples check for AragoDBPedia took 0.8249878883361816s
Interoperability | New terms check for AragoDBPedia took 2.2998766899108887s
Versatility | Languages check for AragoDBPedia took 60.48711276054382s
Interpretability | Number of blank nodes check for AragoDBPedia took 5.272451400756836s
Security | Check HTTPS for AragoDBPedia took 0.26175761222839355s
Interpretability | RDF structures check for AragoDBPedia took 0.6249775886535645s
Versatility | Serialization formats check for AragoDBPedia took 0.9767115116119385s
Availability | RDF dump link check for AragoDBPedia took 0.4627699851989746s
License | MR license check for AragoDBPedia took 0.7402620315551758s
License | HR license check for AragoDBPedia took 7.069819450378418s
Amount of data | Number of property check for AragoDBPedia took 0.4328892230987549s
Understandability | Number of label check for AragoDBPedia took 0.6269004344940186s
Understandability | URI regex check for AragoDBPedia took 1.0139338970184326s
Understandability | Vocabs check for AragoDBPedia took 0.5117239952087402s
Verifiability | Authors check for AragoDBPedia took 0.5406308174133301s
Verifiability | Publishers check for AragoDBPedia took 0.5146403312683105s
Performance | Throughput check for AragoDBPedia took 12.164528608322144s
Amount of data | Check the number of entities for AragoDBPedia took 6.985664367675781e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.5445640087127686s
Interlinking | sameAs chians check for AragoDBPedia took 0.512991189956665s
Interlinking | skos check for AragoDBPedia took 0.731564998626709s
Interlinking | skos check for AragoDBPedia took 0.4224069118499756s
Timeliness | dataset update frequency check for AragoDBPedia took 1.3999567031860352s
Currency | Creation date check for AragoDBPedia took 2.002321720123291s
Currency | Modification date check for AragoDBPedia took 0.9282259941101074s
Rep.Conc. | URIs length for AragoDBPedia took 6.230557918548584s
Interoperability | New vocabularies check for AragoDBPedia took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.43918609619140625s
Accuracy | Check Functional Property for AragoDBPedia took 0.5300335884094238s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.5260450839996338s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.2782018184661865s
Accuracy | Check White space in annotation for AragoDBPedia took 0.027653217315673828s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.02795267105102539s
Consistency | Disjoint class check for AragoDBPedia took 0.4307594299316406s
Consistency | Check Misplaced properties for AragoDBPedia took 4.924453020095825s
Consistency | Misplaced classes for AragoDBPedia took 0.7621099948883057s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.760256290435791s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3146779537200928s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.385453939437866s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.0317537784576416s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.6369936466217041s
Security | Sign check for AragoDBPedia took 0.7258429527282715s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3406.6243081092834s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.6132559776306152s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02112603187561035s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for AragoDBPedia took 4.76837158203125e-06s
INFO | --- Analysis for aragodbpedia took 18711.902928352356s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.28081512451172s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.27500343322753906s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.91278076171875e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for archiveshub-linkeddata took 83.44205641746521s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.3392181396484375e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0003495216369628906s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.2786369323730469s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.024314165115356445s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0011641979217529297s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 5.340576171875e-05s
Believability | Calculation of trust value for Archivi ISMA took 9.298324584960938e-06s
INFO | --- Analysis for archivio-isma took 4.395076513290405s
Availability | SPARQL endpoint availability check for ARIADNE took 4.410743713378906e-05s
Availability | VoID file availability check for ARIADNE took 0.00040602684020996094s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.275479793548584s
Reputation | Calculation of the PageRank for ARIADNE took 0.02416205406188965s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0011839866638183594s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 4.267692565917969e-05s
Believability | Calculation of trust value for ARIADNE took 9.298324584960938e-06s
INFO | --- Analysis for ariadne took 3.0369296073913574s
Availability | SPARQL endpoint availability check for Aristotle University took 4.3392181396484375e-05s
Availability | VoID file availability check for Aristotle University took 0.0003535747528076172s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.2774960994720459s
Reputation | Calculation of the PageRank for Aristotle University took 0.02460646629333496s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0011935234069824219s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 4.267692565917969e-05s
Believability | Calculation of trust value for Aristotle University took 9.059906005859375e-06s
INFO | --- Analysis for aristotle-university took 3.9533491134643555s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.9369213581085205s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2799079418182373s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02445363998413086s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0011858940124511719s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 4.363059997558594e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 8.58306884765625e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 22.592928886413574s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.291534423828125e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00035381317138671875s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.2772700786590576s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.024434566497802734s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0011749267578125s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.315376281738281e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.059906005859375e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 3.0848541259765625s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.917219400405884s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.28275084495544434s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.743171691894531e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 7.867813110351562e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 17.52054452896118s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.2438507080078125e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2732572555541992s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020219802856445312s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010037422180175781s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 8.384029150009155s
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.00027298927307128906s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.28388547897338867s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020073652267456055s
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.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.1444091796875e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 7.3909759521484375e-06s
INFO | --- Analysis for Arthron took 2.4877943992614746s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.1961669921875e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2784886360168457s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00011110305786132812s
Believability | Calculation of trust value for Arthroscopy community took 7.152557373046875e-06s
INFO | --- Analysis for arthroscopy took 3.1114916801452637s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.6083488464355469s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0005726814270019531s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 0.08917880058288574s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 0.0894467830657959s
Versatility | Languages check for Wikidata entry for Art × Science International took 0.08965802192687988s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.09070658683776855s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.0890195369720459s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.09136152267456055s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.08966684341430664s
License | MR license check for Wikidata entry for Art × Science International took 0.09315609931945801s
License | HR license check for Wikidata entry for Art × Science International took 0.08902549743652344s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.09246230125427246s
Understandability | Number of label check for Wikidata entry for Art × Science International took 0.09173130989074707s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.18192720413208008s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.09194207191467285s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.08941841125488281s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.09162425994873047s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.00014162063598632812s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.08964657783508301s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.09096789360046387s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.08950066566467285s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.09845757484436035s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.09157133102416992s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.18407082557678223s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.1805107593536377s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 0.18045926094055176s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.09754586219787598s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.09230351448059082s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.09096455574035645s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.463615894317627s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 0.0007481575012207031s
Security | Sign check for Wikidata entry for Art × Science International took 0.09152436256408691s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.2722938060760498s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020020008087158203s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 4.76837158203125e-07s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 6.9141387939453125e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 18.220555305480957s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.0246078968048096s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.27257275581359863s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.486343383789062e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 12.024361848831177s
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.276364803314209s
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.0005788803100585938s
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.27471041679382324s
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.02014899253845215s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0007281303405761719s
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 8.0108642578125e-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.152557373046875e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 10.786654472351074s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.2641525268554688s
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.2742655277252197s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.02016305923461914s
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.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.559226989746094e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 11.784676313400269s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.267975330352783s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.7500603199005127s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 3.981590270996094e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-CRB took 14.683284282684326s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.2619614601135254s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2772495746612549s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.821487426757812e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.641767024993896s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.2654690742492676s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.372692346572876s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.02033543586730957s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.504753112792969e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.86561894416809s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.262132406234741s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2762901782989502s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.414817810058594e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.290473699569702s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 7.024785041809082s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.27898359298706055s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.62939453125e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 17.04095196723938s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.2643771171569824s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.28293561935424805s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020071983337402344s
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.5367431640625e-06s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.602836608886719e-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.3909759521484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.269116163253784s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.266603946685791s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2783207893371582s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.340576171875e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.264111280441284s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.8457953929901123s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2733602523803711s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020041465759277344s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.410743713378906e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 15.541524648666382s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.268493890762329s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2804896831512451s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.390975952148438e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 10.765871047973633s
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.2673215866088867s
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.0007100105285644531s
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.2806072235107422s
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.02057671546936035s
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.239776611328125e-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.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.821487426757812e-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 8.106231689453125e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.282662868499756s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.265016555786133s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.28097057342529297s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC_-_DNB took 10.779079914093018s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.291534423828125e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.27060365676879883s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.580352783203125e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 8.344650268554688e-06s
INFO | --- Analysis for asit took 8.381293773651123s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.1961669921875e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.27327418327331543s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.022522926330566406s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.363059997558594e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.62939453125e-06s
INFO | --- Analysis for asjp took 5.7112202644348145s
Availability | SPARQL endpoint availability check for ASN:US took 523.2657558917999s
Availability | VoID file availability check for ASN:US took 0.0009050369262695312s
Completeness | Calculation of interlinking completeness for ASN:US took 0.7107031345367432s
Reputation | Calculation of the PageRank for ASN:US took 0.025440216064453125s
Interlinking | Calculation of Degree of Connection for ASN:US took 3.647804260253906e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0012264251708984375s
Interlinking | Calculation of Clustering coefficient for ASN:US took 0.00010275840759277344s
Believability | Calculation of trust value for ASN:US took 6.4373016357421875e-06s
INFO | --- Analysis for asn-us took 1338.5426959991455s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.6253204345703125e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.7151350975036621s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.0040740966796875e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 5.0067901611328125e-06s
INFO | --- Analysis for aspire-mmu took 6.858003377914429s
Availability | SPARQL endpoint availability check for associations took 4.267692565917969e-05s
Availability | VoID file availability check for associations took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for associations took 0.7216925621032715s
Reputation | Calculation of the PageRank for associations took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for associations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for associations took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for associations took 6.67572021484375e-05s
Believability | Calculation of trust value for associations took 7.152557373046875e-06s
INFO | --- Analysis for associations took 7.89479398727417s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.220008850097656e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.27479124069213867s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020193099975585938s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.8848648071289062e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 6.9141387939453125e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 3.483686685562134s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 5.221366882324219e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.27687764167785645s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.131431579589844e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 5.9604644775390625e-06s
INFO | --- Analysis for athelia-rfid took 4.528277635574341s
Availability | SPARQL endpoint availability check for AuditSocials Social Media Advertising Compliance Glossary took 4.1484832763671875e-05s
Availability | VoID file availability check for AuditSocials Social Media Advertising Compliance Glossary took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for AuditSocials Social Media Advertising Compliance Glossary took 0.27355265617370605s
Reputation | Calculation of the PageRank for AuditSocials Social Media Advertising Compliance Glossary took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for AuditSocials Social Media Advertising Compliance Glossary took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for AuditSocials Social Media Advertising Compliance Glossary took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for AuditSocials Social Media Advertising Compliance Glossary took 1.2159347534179688e-05s
Believability | Calculation of trust value for AuditSocials Social Media Advertising Compliance Glossary took 6.9141387939453125e-06s
INFO | --- Analysis for auditsocials-glossary took 4.068079710006714s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.029273986816406e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2719764709472656s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020335674285888672s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.86102294921875e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for aueb-linked-open-data took 3.46376371383667s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5480766296386719s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2814638614654541s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02004384994506836s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.649162292480469e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for AugustiniConfessiones took 4.078970670700073s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6404526233673096s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.27854251861572266s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020061969757080078s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.58306884765625e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 6.4373016357421875e-06s
INFO | --- Analysis for austrian_ski_racers took 3.866806745529175s
Availability | SPARQL endpoint availability check for AVsOnto took 4.220008850097656e-05s
Availability | VoID file availability check for AVsOnto took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.39104461669921875s
Reputation | Calculation of the PageRank for AVsOnto took 0.020209789276123047s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 2.6941299438476562e-05s
Believability | Calculation of trust value for AVsOnto took 6.67572021484375e-06s
INFO | --- Analysis for AVsOnto took 3.47268009185791s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21416306495666504s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005147457122802734s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 206.21394634246826s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5263772010803223s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.04360127449036s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 276.62854075431824s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0191841125488s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0474488735199s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2648608684539795s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25933146476745605s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19744491577148438s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10742640495300293s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 51.139020919799805s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10339307785034s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15575480461120605s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06381607055664s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24291372299194336s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17704129219055176s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10991358757019043s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13637638092041016s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.394432783126831s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.463859558105469e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10891580581665039s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0313060283661s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17617201805114746s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13653850555419922s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19716286659240723s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2704501152038574s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2551097869873047s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 678.2836277484894s
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.15866351127624512s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 32.22377800941467s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1977384090423584s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.843620300292969s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16312742233276367s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1636230945587s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 34.72689604759216s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.427074432373047s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.50373220443726s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.814422130584717s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17730450630187988s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.275083065032959s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.36902785301208496s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02393317222595215s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.152557373046875e-06s
INFO | --- Analysis for b3kat took 4338.062976837158s
Availability | SPARQL endpoint availability check for BabelNet took 0.43067169189453125s
Availability | VoID file availability check for BabelNet took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for BabelNet took 0.2830791473388672s
Reputation | Calculation of the PageRank for BabelNet took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0008497238159179688s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00017380714416503906s
Believability | Calculation of trust value for BabelNet took 7.867813110351562e-06s
INFO | --- Analysis for babelnet took 6.37415337562561s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.076957702636719e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.2724156379699707s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.021344900131225586s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.337860107421875e-05s
Believability | Calculation of trust value for Bacevicius.lt took 7.62939453125e-06s
INFO | --- Analysis for Bacevicius.lt took 2.466334342956543s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5310559272766113s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2765045166015625s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.9591064453125e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 6.9141387939453125e-06s
INFO | --- Analysis for bag took 4.485443115234375s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.5882258415222168s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002124309539794922s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.27784180641174316s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.123283386230469e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 3.170967102050781e-05s
INFO | --- Analysis for baixue took 3.950974941253662s
Availability | SPARQL endpoint availability check for baixue composer took 5.245208740234375e-05s
Availability | VoID file availability check for baixue composer took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for baixue composer took 0.28569674491882324s
Reputation | Calculation of the PageRank for baixue composer took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.0279159545898438e-05s
Believability | Calculation of trust value for baixue composer took 6.4373016357421875e-06s
INFO | --- Analysis for baixue_composer took 3.0047497749328613s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.91278076171875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2689511775970459s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.026449918746948242s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0012974739074707031s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.910064697265625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.152557373046875e-06s
INFO | --- Analysis for baixue_imagery took 3.138359785079956s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.1021575927734375e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.28205251693725586s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.075599670410156e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 5.7220458984375e-06s
INFO | --- Analysis for baixue_imagery1 took 3.5103776454925537s
Availability | SPARQL endpoint availability check for BAMS took 4.100799560546875e-05s
Availability | VoID file availability check for BAMS took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for BAMS took 0.28046083450317383s
Reputation | Calculation of the PageRank for BAMS took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for BAMS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.0517578125e-05s
Believability | Calculation of trust value for BAMS took 7.62939453125e-06s
INFO | --- Analysis for bams took 3.042480707168579s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.2438507080078125e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.27460217475891113s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02057337760925293s
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.0011513233184814453s
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 8.106231689453125e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.0757837295532227s
Availability | SPARQL endpoint availability check for BBC Music took 0.31064748764038086s
Availability | VoID file availability check for BBC Music took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for BBC Music took 0.280698299407959s
Reputation | Calculation of the PageRank for BBC Music took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013136863708496094s
Believability | Calculation of trust value for BBC Music took 7.3909759521484375e-06s
INFO | --- Analysis for bbc-music took 3.561610221862793s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.24398136138916016s
Availability | VoID file availability check for BBC Programmes took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.27570533752441406s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00011134147644042969s
Believability | Calculation of trust value for BBC Programmes took 7.62939453125e-06s
INFO | --- Analysis for bbc-programmes took 11.583803653717041s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.24959731101989746s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.28292369842529297s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.021867990493774414s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00011134147644042969s
Believability | Calculation of trust value for BBC Wildlife Finder took 6.67572021484375e-06s
INFO | --- Analysis for bbc-wildlife-finder took 10.428687810897827s
Availability | SPARQL endpoint availability check for BBOP took 4.220008850097656e-05s
Availability | VoID file availability check for BBOP took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for BBOP took 0.2778170108795166s
Reputation | Calculation of the PageRank for BBOP took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for BBOP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.0279159545898438e-05s
Believability | Calculation of trust value for BBOP took 6.198883056640625e-06s
INFO | --- Analysis for bbop took 3.0227272510528564s
Availability | SPARQL endpoint availability check for BBOP took 5.7697296142578125e-05s
Availability | VoID file availability check for BBOP took 0.001028299331665039s
Completeness | Calculation of interlinking completeness for BBOP took 0.28098440170288086s
Reputation | Calculation of the PageRank for BBOP took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for BBOP took 4.124641418457031e-05s
Believability | Calculation of trust value for BBOP took 8.344650268554688e-06s
INFO | --- Analysis for bbop-selected took 21.0309476852417s
Availability | SPARQL endpoint availability check for Bdgp took 1.60794997215271s
Availability | VoID file availability check for Bdgp took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2715022563934326s
Reputation | Calculation of the PageRank for Bdgp took 0.021474838256835938s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0010461807250976562s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.8623809814453125e-05s
Believability | Calculation of trust value for Bdgp took 7.867813110351562e-06s
INFO | --- Analysis for bdgp took 8.496940851211548s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.315376281738281e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.2783164978027344s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.170967102050781e-05s
Believability | Calculation of trust value for Bendev Junior took 6.67572021484375e-06s
INFO | --- Analysis for bendevoficial took 5.37905478477478s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.9004411697387695s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.27820849418640137s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02038121223449707s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.508827209472656e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 4.0531158447265625e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 13.421918153762817s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 3.8623809814453125e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.2764017581939697s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020338058471679688s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.170967102050781e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 5.9604644775390625e-06s
INFO | --- Analysis for berlin-offener-haushalt took 3.030968427658081s
Availability | SPARQL endpoint availability check for berlios took 4.00543212890625e-05s
Availability | VoID file availability check for berlios took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for berlios took 0.27280092239379883s
Reputation | Calculation of the PageRank for berlios took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for berlios took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for berlios took 8.726119995117188e-05s
Believability | Calculation of trust value for berlios took 8.821487426757812e-06s
INFO | --- Analysis for berlios took 3.0926356315612793s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.6253204345703125e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.33522963523864746s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.771087646484375e-05s
Believability | Calculation of trust value for Between Our Worlds took 7.3909759521484375e-06s
INFO | --- Analysis for betweenourworlds took 9.542381048202515s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.4004542827606201s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.001132965087890625s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.29003429412841797s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.059906005859375e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 3.528594970703125e-05s
INFO | --- Analysis for bfs-linked-data took 3.062666893005371s
Availability | SPARQL endpoint availability check for BibBase took 0.07170987129211426s
Availability | VoID file availability check for BibBase took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for BibBase took 0.2780120372772217s
Reputation | Calculation of the PageRank for BibBase took 0.0208737850189209s
Interlinking | Calculation of Degree of Connection for BibBase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.489059448242188e-05s
Believability | Calculation of trust value for BibBase took 1.8835067749023438e-05s
INFO | --- Analysis for bibbase took 2.581404685974121s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 5.626678466796875e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.27582406997680664s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.822845458984375e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 5.0067901611328125e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 5.5190794467926025s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.220008850097656e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.272594690322876s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010442733764648438s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 3.0757291316986084s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 5.817413330078125e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.27244997024536133s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 6.4373016357421875e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 3.024353504180908s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.124641418457031e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.27777910232543945s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.552436828613281e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 6.198883056640625e-06s
INFO | --- Analysis for BibSonomy took 7.650973081588745s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.1961669921875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2786839008331299s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.2901763916015625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 5.9604644775390625e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.07703709602356s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.100799560546875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.27141332626342773s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.218650817871094e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 5.7220458984375e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 3.0350546836853027s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2736642360687256s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-acfsid took 3.0485825538635254s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 39.01945495605469s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.3214879035949707s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010609626770019531s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 139.08112263679504s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 39.01982569694519s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.2729790210723877s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.021361827850341797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012540817260742188s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-biomodels took 139.60511326789856s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.2790195941925049s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.373157978057861s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 39.0191011428833s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.333634614944458s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.021117687225341797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004124641418457031s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-bioportal took 180.64557313919067s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 39.0212140083313s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.27780699729919434s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.984306335449219e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-chembl took 179.44170880317688s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 39.02217102050781s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0004177093505859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.7971079349517822s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.792213439941406e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 180.0742506980896s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 39.02247643470764s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.37090539932250977s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020192384719848633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.4849853515625e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-ctd took 140.54378581047058s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 5.269050598144531e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.00040221214294433594s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.26756954193115234s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.03266000747680664s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0013928413391113281s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 6.198883056640625e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-dataset took 23.041698932647705s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 39.021822929382324s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 1.2190115451812744s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.02098536491394043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.224082946777344e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 180.95328426361084s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 39.01867079734802s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.7051780223846436s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010085105895996094s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-drugbank took 141.49713253974915s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 39.02299094200134s
Availability | VoID file availability check for Bio2RDF::Genage took 0.00031828880310058594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.7401888370513916s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.8650970458984375e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-genage took 179.72678542137146s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.3392181396484375e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.2738182544708252s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.8650970458984375e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-genbank took 3.4443202018737793s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 39.024319648742676s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.2788567543029785s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 4.792213439941406e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-gendr took 179.57002353668213s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 39.02182960510254s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.3638617992401123s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.602836608886719e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-goa took 139.9995858669281s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 39.02447056770325s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.28331780433654785s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011730194091796875s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-hgnc took 139.9221441745758s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 39.01731848716736s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.28150200843811035s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 6.318092346191406e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-homologene took 140.2153377532959s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.7003233432769775s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-inoh took 3.440901041030884s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 39.021148443222046s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.733407735824585s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010013580322265625s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-interpro took 140.39824175834656s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 39.024118423461914s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.7937352657318115s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 8.749961853027344e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-iproclass took 181.31697916984558s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 39.024696350097656s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.6939098834991455s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02021932601928711s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.606910705566406e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-irefindex took 141.2058389186859s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.2739682197570801s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.02103257179260254s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 7.414817810058594e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-kegg took 3.4482674598693848s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2808043956756592s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0009615421295166016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 4.076957702636719e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.0313403606414795s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 39.022889137268066s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2817509174346924s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02021479606628418s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 140.30955624580383s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 39.0246901512146s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.8258757591247559s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.1961669921875e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-lsr took 140.8716917037964s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 39.021997928619385s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.34849047660827637s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.390975952148438e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-mesh took 140.0064239501953s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 39.01673674583435s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.27829527854919434s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 8.940696716308594e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 5.7220458984375e-06s
INFO | --- Analysis for bio2rdf-mgi took 179.77880668640137s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 39.02214598655701s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.797137975692749s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012063980102539062s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 181.69199895858765s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 39.020949363708496s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.7156069278717041s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.482269287109375e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ndc took 141.5594928264618s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.2920973300933838s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-netpath took 4.376742839813232s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 39.009116411209106s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.27812910079956055s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-nextprot took 100.00548911094666s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 39.02528762817383s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.27404046058654785s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013446807861328125s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-omim took 140.74643468856812s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 6.937980651855469e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2972095012664795s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.6716461181640625e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 23.387914180755615s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 39.01737666130066s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.2853829860687256s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.724761962890625e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-orphanet took 139.94718766212463s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 39.02197861671448s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.7520818710327148s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 141.32479429244995s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 39.021798849105835s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.2918119430541992s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 0.00010824203491210938s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 140.04286789894104s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.27541136741638184s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 3.9153473377227783s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.28011631965637207s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pid took 3.036278247833252s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.3392181396484375e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.27358031272888184s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.5056254863739014s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 39.022895097732544s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.312363862991333s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020153284072875977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00012969970703125s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 140.38417720794678s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.7124667167663574s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.604194641113281e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-reactome took 3.930266857147217s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.4345855712890625e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.276944637298584s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.3882598876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.0480363368988037s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 39.02621364593506s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.2749936580657959s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.748603820800781e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 5.4836273193359375e-06s
INFO | --- Analysis for bio2rdf-sabiork took 140.69264793395996s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 39.01925587654114s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.3391587734222412s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.02071237564086914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010967254638671875s
Believability | Calculation of trust value for Bio2RDF::Sgd took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-sgd took 140.39736938476562s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.220008850097656e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.7006814479827881s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.028361797332763672s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0013623237609863281s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 4.982948303222656e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 23.466033220291138s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 39.023642778396606s
Availability | VoID file availability check for Bio2RDF::Sider took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.27571630477905273s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.021069765090942383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.220008850097656e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-sider took 139.88308548927307s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 3.8623809814453125e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.2809915542602539s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-spike took 3.53519868850708s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.0531158447265625e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2786257266998291s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.315376281738281e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-taxon took 22.92089819908142s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 39.019758224487305s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.7578830718994141s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.0001010894775390625s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 140.27808499336243s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 39.01778268814087s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.27754926681518555s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02079606056213379s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 4.3392181396484375e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 179.72265243530273s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 39.02322483062744s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.3702981472015381s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.153915405273438e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-wormbase took 180.37517714500427s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.2438507080078125e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.27786779403686523s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.02264094352722168s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 4.0531158447265625e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.001459360122680664s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.71661376953125e-05s
Believability | Calculation of trust value for Biografías y Vidas took 7.62939453125e-06s
INFO | --- Analysis for biografiasyvidas took 2.9217147827148438s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.2572779655456543s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.27680110931396484s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020066499710083008s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.177757263183594e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 4.76837158203125e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 2.77028751373291s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.124641418457031e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.2750272750854492s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.8848648071289062e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for biolit took 3.524325370788574s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.029273986816406e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.27656030654907227s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.695487976074219e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 5.7220458984375e-06s
INFO | --- Analysis for biolod-pdb took 8.199468612670898s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.7505970001220703s
Availability | VoID file availability check for BioModels RDF took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.26764798164367676s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for BioModels RDF took 5.7220458984375e-06s
INFO | --- Analysis for biomodels-rdf took 4.318646669387817s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.893831253051758s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2840006351470947s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.170967102050781e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.8835067749023438e-05s
INFO | --- Analysis for Biop took 7.4254889488220215s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.6253204345703125e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.27932214736938477s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02017498016357422s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.218650817871094e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 6.198883056640625e-06s
INFO | --- Analysis for Bioportal took 2.559849977493286s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 0.00011491775512695312s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2768101692199707s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020253896713256836s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006241798400878906s
Believability | Calculation of trust value for Amphibian gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-aao took 2.8577563762664795s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.839897155761719e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2761421203613281s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02025008201599121s
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.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002791881561279297s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-aba took 2.711500883102417s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.28040599822998047s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015454292297363281s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-acgt took 3.226710081100464s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.458427429199219e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2804887294769287s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003273487091064453s
Believability | Calculation of trust value for Animal natural history and life history took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-adw took 2.8092267513275146s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.2768065929412842s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004611015319824219s
Believability | Calculation of trust value for Anatomical Entity Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-aeo took 2.7055070400238037s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2756519317626953s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020964860916137695s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009860992431640625s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-aero took 2.76328444480896s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.458427429199219e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2787773609161377s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003800392150878906s
Believability | Calculation of trust value for AI/RHEUM took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-air took 2.7179911136627197s
Availability | SPARQL endpoint availability check for Amino Acid took 4.076957702636719e-05s
Availability | VoID file availability check for Amino Acid took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.2769312858581543s
Reputation | Calculation of the PageRank for Amino Acid took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00026035308837890625s
Believability | Calculation of trust value for Amino Acid took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.720640182495117s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.76837158203125e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.276289701461792s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00027823448181152344s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-apo took 2.730461835861206s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.1484832763671875e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2780337333679199s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00022983551025390625s
Believability | Calculation of trust value for African Traditional Medicine took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-atmo took 2.7365827560424805s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.124641418457031e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2777400016784668s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.298324584960938e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ato took 2.6659467220306396s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2730536460876465s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.001316070556640625s
Believability | Calculation of trust value for BioAssay Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bao took 2.7203338146209717s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.28433656692504883s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003662109375s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.7417662143707275s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.27497076988220215s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00030994415283203125s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bcgo took 2.7034952640533447s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.28347039222717285s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014045238494873047s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bdo took 2.7062675952911377s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.27332162857055664s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004987716674804688s
Believability | Calculation of trust value for Basic Formal Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bfo took 2.650404214859009s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.2438507080078125e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2721138000488281s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007131099700927734s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bho took 2.717474937438965s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.1484832763671875e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2734065055847168s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0010669231414794922s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0005011558532714844s
Believability | Calculation of trust value for Bilateria anatomy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bila took 2.7105681896209717s
Availability | SPARQL endpoint availability check for BIRNLex took 4.076957702636719e-05s
Availability | VoID file availability check for BIRNLex took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2765696048736572s
Reputation | Calculation of the PageRank for BIRNLex took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0015034675598144531s
Believability | Calculation of trust value for BIRNLex took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-birnlex took 2.701312303543091s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 5.7220458984375e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2796816825866699s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020748138427734375s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007557868957519531s
Believability | Calculation of trust value for Gene Regulation Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.687130928039551s
Availability | SPARQL endpoint availability check for BioPAX took 4.1961669921875e-05s
Availability | VoID file availability check for BioPAX took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for BioPAX took 0.28795528411865234s
Reputation | Calculation of the PageRank for BioPAX took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.465217590332031e-05s
Believability | Calculation of trust value for BioPAX took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bp took 2.7010374069213867s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.27636098861694336s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020242929458618164s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003159046173095703s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.679871082305908s
Availability | SPARQL endpoint availability check for Spatial Ontology took 7.319450378417969e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.2748074531555176s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00021958351135253906s
Believability | Calculation of trust value for Spatial Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bspo took 2.6747500896453857s
Availability | SPARQL endpoint availability check for BioTop took 4.363059997558594e-05s
Availability | VoID file availability check for BioTop took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for BioTop took 0.27700161933898926s
Reputation | Calculation of the PageRank for BioTop took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006527900695800781s
Believability | Calculation of trust value for BioTop took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bt took 2.7201735973358154s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.220008850097656e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.28272032737731934s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008637905120849609s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bto took 2.758765459060669s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3281557559967041s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02047562599182129s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018911361694335938s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-canco took 3.1837949752807617s
Availability | SPARQL endpoint availability check for CAO took 5.3882598876953125e-05s
Availability | VoID file availability check for CAO took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for CAO took 0.27753686904907227s
Reputation | Calculation of the PageRank for CAO took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for CAO took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006561279296875s
Believability | Calculation of trust value for CAO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cao took 2.72299861907959s
Availability | SPARQL endpoint availability check for CareLex took 4.1961669921875e-05s
Availability | VoID file availability check for CareLex took 0.0010221004486083984s
Completeness | Calculation of interlinking completeness for CareLex took 0.2756385803222656s
Reputation | Calculation of the PageRank for CareLex took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for CareLex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.553794860839844e-05s
Believability | Calculation of trust value for CareLex took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-carelex took 2.7426180839538574s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.27998924255371094s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02020859718322754s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007753372192382812s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cco took 2.7217655181884766s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2714400291442871s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.000274658203125s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cdao took 2.7092297077178955s
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.0005114078521728516s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2756779193878174s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020007848739624023s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007715225219726562s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-chebi took 2.7340822219848633s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.1961669921875e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.28160595893859863s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020076751708984375s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002541542053222656s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.7122716903686523s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.2793996334075928s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020038604736328125s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007541179656982422s
Believability | Calculation of trust value for Chemical Information Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cheminf took 2.734670877456665s
Availability | SPARQL endpoint availability check for Cell type took 4.1484832763671875e-05s
Availability | VoID file availability check for Cell type took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Cell type took 0.2715632915496826s
Reputation | Calculation of the PageRank for Cell type took 0.02012348175048828s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003752708435058594s
Believability | Calculation of trust value for Cell type took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cl took 2.672011137008667s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.28217649459838867s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.019967317581176758s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0007953643798828125s
Believability | Calculation of trust value for Cell Line Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-clo took 2.718552350997925s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.27834105491638184s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02995586395263672s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0009374618530273438s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00020241737365722656s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cmo took 2.747878313064575s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.27968621253967285s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02013707160949707s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020122528076171875s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cno took 2.7386763095855713s
Availability | SPARQL endpoint availability check for Wheat trait took 4.100799560546875e-05s
Availability | VoID file availability check for Wheat trait took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.2752232551574707s
Reputation | Calculation of the PageRank for Wheat trait took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 4.9114227294921875e-05s
Believability | Calculation of trust value for Wheat trait took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.7255325317382812s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 5.269050598144531e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.28052234649658203s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003566741943359375s
Believability | Calculation of trust value for Cognitive Atlas took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cogat took 2.754672050476074s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 5.1975250244140625e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2700037956237793s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007846355438232422s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cogpo took 2.6892268657684326s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.1961669921875e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2771735191345215s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004143714904785156s
Believability | Calculation of trust value for Current Procedural Terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cpt took 2.7023839950561523s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.267692565917969e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3254671096801758s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017437934875488281s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-csp took 3.1393704414367676s
Availability | SPARQL endpoint availability check for COSTART took 7.104873657226562e-05s
Availability | VoID file availability check for COSTART took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for COSTART took 0.2752978801727295s
Reputation | Calculation of the PageRank for COSTART took 0.020249366760253906s
Interlinking | Calculation of Degree of Connection for COSTART took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009675025939941406s
Believability | Calculation of trust value for COSTART took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cst took 2.7109458446502686s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.0531158447265625e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.27663707733154297s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020229578018188477s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.00051116943359375s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ctcae took 2.7144882678985596s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.124641418457031e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0011813640594482422s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.28201794624328613s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00043320655822753906s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ctx took 2.718101978302002s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.100799560546875e-05s
Availability | VoID file availability check for Dendritic cell took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.27117013931274414s
Reputation | Calculation of the PageRank for Dendritic cell took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00028204917907714844s
Believability | Calculation of trust value for Dendritic cell took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.7064907550811768s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2689368724822998s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.0200655460357666s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.606910705566406e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ddanat took 2.6933751106262207s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2742345333099365s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.000949859619140625s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ddi took 2.7138519287109375s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2789599895477295s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.01999831199645996s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.344650268554688e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.684201717376709s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.27882909774780273s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.019927263259887695s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00015544891357421875s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.7242841720581055s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.28340816497802734s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006105899810791016s
Believability | Calculation of trust value for Human disease ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-doid took 2.710482358932495s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.26698923110961914s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020255565643310547s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007889270782470703s
Believability | Calculation of trust value for Electrocardiography Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ecg took 2.7081706523895264s
Availability | SPARQL endpoint availability check for Evidence codes took 4.076957702636719e-05s
Availability | VoID file availability check for Evidence codes took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2764623165130615s
Reputation | Calculation of the PageRank for Evidence codes took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0008542537689208984s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.4332275390625e-05s
Believability | Calculation of trust value for Evidence codes took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-eco took 2.7196524143218994s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.33353137969970703s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017349720001220703s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-efo took 3.1511967182159424s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.1961669921875e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.272263765335083s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011560916900634766s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ehda took 2.7017478942871094s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.100799560546875e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.27634334564208984s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007126331329345703s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.696495771408081s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.267692565917969e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.28007960319519043s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020087242126464844s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005049705505371094s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.672746181488037s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.172325134277344e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.28046655654907227s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.9325485229492188e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-emap took 2.7100255489349365s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Environment Ontology took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2695810794830322s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0003838539123535156s
Believability | Calculation of trust value for Environment Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-envo took 2.7144269943237305s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 6.437301635742188e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2786829471588135s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00032067298889160156s
Believability | Calculation of trust value for Plant environmental conditions took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-eo took 2.709017038345337s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 5.507469177246094e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.27575087547302246s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012128353118896484s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ep took 2.730292320251465s
Availability | SPARQL endpoint availability check for Epilepsy took 4.076957702636719e-05s
Availability | VoID file availability check for Epilepsy took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.27866101264953613s
Reputation | Calculation of the PageRank for Epilepsy took 0.01992034912109375s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00011944770812988281s
Believability | Calculation of trust value for Epilepsy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-epileponto took 2.712125062942505s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.267692565917969e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2802774906158447s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.03596210479736328s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0012350082397460938s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0014345645904541016s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ero took 2.7536439895629883s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.315376281738281e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2789797782897949s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.019954681396484375s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.001119375228881836s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ev took 2.749631404876709s
Availability | SPARQL endpoint availability check for ExO took 4.0531158447265625e-05s
Availability | VoID file availability check for ExO took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for ExO took 0.27191925048828125s
Reputation | Calculation of the PageRank for ExO took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for ExO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00024127960205078125s
Believability | Calculation of trust value for ExO took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-exo took 2.704158067703247s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.0531158447265625e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.28369832038879395s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.021271705627441406s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00012302398681640625s
Believability | Calculation of trust value for Fungal gross anatomy took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-fao took 2.760671854019165s
Availability | SPARQL endpoint availability check for Biological imaging methods took 5.269050598144531e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2801506519317627s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02001476287841797s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00017762184143066406s
Believability | Calculation of trust value for Biological imaging methods took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fbbi took 2.757835626602173s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.27739453315734863s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020132780075073242s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0008232593536376953s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006284713745117188s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fbbt took 2.838594436645508s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.100799560546875e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.28297901153564453s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004315376281738281s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fbcv took 2.7530694007873535s
Availability | SPARQL endpoint availability check for Drosophila development took 7.653236389160156e-05s
Availability | VoID file availability check for Drosophila development took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.27726078033447266s
Reputation | Calculation of the PageRank for Drosophila development took 0.0202481746673584s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.6253204345703125e-05s
Believability | Calculation of trust value for Drosophila development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbdv took 2.6894819736480713s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.291534423828125e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2794678211212158s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02045297622680664s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003857612609863281s
Believability | Calculation of trust value for Fly taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbsp took 2.72639799118042s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.100799560546875e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.27388691902160645s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00021719932556152344s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.711179733276367s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2742626667022705s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0003898143768310547s
Believability | Calculation of trust value for Family Health History Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fhho took 2.711791515350342s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.27870702743530273s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010378360748291016s
Believability | Calculation of trust value for Influenza Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-flu took 2.711895227432251s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 5.602836608886719e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2719719409942627s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007178783416748047s
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.245208740234375e-06s
INFO | --- Analysis for bioportal-fma took 2.6664934158325195s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2761406898498535s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001418590545654297s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fypo took 2.6807892322540283s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.28121280670166016s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0010225772857666016s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.00011920928955078125s
Believability | Calculation of trust value for GeoSpecies Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-geospecies took 2.7166011333465576s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for General Formal Ontology took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2809441089630127s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016832351684570312s
Believability | Calculation of trust value for General Formal Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-gfo took 2.7301175594329834s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.1484832763671875e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2796058654785156s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005903244018554688s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.7770819664001465s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.076957702636719e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.27751660346984863s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.0202786922454834s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008604526519775391s
Believability | Calculation of trust value for Gene Ontology Extension took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.708589792251587s
Availability | SPARQL endpoint availability check for Gene Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2779874801635742s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020558595657348633s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0008285045623779297s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0009100437164306641s
Believability | Calculation of trust value for Gene Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.7182462215423584s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.00543212890625e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.27655935287475586s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020259380340576172s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.0279159545898438e-05s
Believability | Calculation of trust value for Cereal Plant Development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gro took 2.7425057888031006s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.1484832763671875e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2841503620147705s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0005214214324951172s
Believability | Calculation of trust value for Cereal plant gross anatomy took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.7291598320007324s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 5.2928924560546875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.27692532539367676s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020192623138427734s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007350444793701172s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.70637845993042s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.28050875663757324s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005424022674560547s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hao took 2.7317237854003906s
Availability | SPARQL endpoint availability check for HCPCS took 4.124641418457031e-05s
Availability | VoID file availability check for HCPCS took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for HCPCS took 0.27613401412963867s
Reputation | Calculation of the PageRank for HCPCS took 0.020120620727539062s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00021719932556152344s
Believability | Calculation of trust value for HCPCS took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.7097055912017822s
Availability | SPARQL endpoint availability check for Health Level Seven took 5.412101745605469e-05s
Availability | VoID file availability check for Health Level Seven took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2783811092376709s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.001264333724975586s
Believability | Calculation of trust value for Health Level Seven took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-hl7 took 2.7109298706054688s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.315376281738281e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2716953754425049s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00033473968505859375s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.7423627376556396s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.27979493141174316s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.031485557556152344s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0013768672943115234s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 4.673004150390625e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hom took 2.7428605556488037s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.1961669921875e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2845737934112549s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.123283386230469e-05s
Believability | Calculation of trust value for HOM-HARVARD took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.6990208625793457s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0010390281677246094s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.27437496185302734s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006315708160400391s
Believability | Calculation of trust value for Human Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.7567129135131836s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.28064393997192383s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010607242584228516s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hpio took 2.769899845123291s
Availability | SPARQL endpoint availability check for HUGO took 4.2438507080078125e-05s
Availability | VoID file availability check for HUGO took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for HUGO took 0.27877259254455566s
Reputation | Calculation of the PageRank for HUGO took 0.020151853561401367s
Interlinking | Calculation of Degree of Connection for HUGO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.796287536621094e-05s
Believability | Calculation of trust value for HUGO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hugo took 2.6771678924560547s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.27260494232177734s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020883798599243164s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006680488586425781s
Believability | Calculation of trust value for Information Artifact Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-iao took 2.6774356365203857s
Availability | SPARQL endpoint availability check for ICD10 took 4.076957702636719e-05s
Availability | VoID file availability check for ICD10 took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for ICD10 took 0.27672743797302246s
Reputation | Calculation of the PageRank for ICD10 took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007927417755126953s
Believability | Calculation of trust value for ICD10 took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-icd10 took 2.733253240585327s
Availability | SPARQL endpoint availability check for ICD10CM took 4.315376281738281e-05s
Availability | VoID file availability check for ICD10CM took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.27040553092956543s
Reputation | Calculation of the PageRank for ICD10CM took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0005972385406494141s
Believability | Calculation of trust value for ICD10CM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.7033023834228516s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.124641418457031e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.27461791038513184s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00014543533325195312s
Believability | Calculation of trust value for ICD-10-PCS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.7008895874023438s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.1961669921875e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.001209259033203125s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.27732181549072266s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020183086395263672s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006198883056640625s
Believability | Calculation of trust value for International Classification of Diseases took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.7065815925598145s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.2438507080078125e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.27555298805236816s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004265308380126953s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.6861538887023926s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.220008850097656e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.269639253616333s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.001293182373046875s
Believability | Calculation of trust value for International Classification for Nursing Practice took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icnp took 2.697392463684082s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 6.365776062011719e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.28669309616088867s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020138978958129883s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004360675811767578s
Believability | Calculation of trust value for International Classification of Primary Care took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-icpc took 2.7159383296966553s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.1484832763671875e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.27558040618896484s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020183563232421875s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008530616760253906s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.7211666107177734s
Availability | SPARQL endpoint availability check for ICPS Network took 4.124641418457031e-05s
Availability | VoID file availability check for ICPS Network took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.27951979637145996s
Reputation | Calculation of the PageRank for ICPS Network took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00023889541625976562s
Believability | Calculation of trust value for ICPS Network took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-icps took 2.6998703479766846s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2866377830505371s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008738040924072266s
Believability | Calculation of trust value for Infectious Disease Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ido took 2.7176454067230225s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 8.20159912109375e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2646465301513672s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02010369300842285s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011601448059082031s
Believability | Calculation of trust value for Brucellosis Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-idobru took 2.6373343467712402s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2721836566925049s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0008168220520019531s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.001346588134765625s
Believability | Calculation of trust value for Malaria Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-idomal took 2.814891815185547s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 7.104873657226562e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.28075242042541504s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0009164810180664062s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00034427642822265625s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-iev took 2.6664817333221436s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 5.459785461425781e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2770810127258301s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00016164779663085938s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-imgt took 2.684748411178589s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 3.9577484130859375e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.27759313583374023s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005033016204833984s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-imr took 2.710897922515869s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2751424312591553s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007898807525634766s
Believability | Calculation of trust value for Interaction Network Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ino took 2.7271246910095215s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.1484832763671875e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2783207893371582s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.9325485229492188e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.690714120864868s
Availability | SPARQL endpoint availability check for IxnO took 4.100799560546875e-05s
Availability | VoID file availability check for IxnO took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for IxnO took 0.27864646911621094s
Reputation | Calculation of the PageRank for IxnO took 0.020114898681640625s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018668174743652344s
Believability | Calculation of trust value for IxnO took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ixno took 2.7381255626678467s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.100799560546875e-05s
Availability | VoID file availability check for SysMO-JERM took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2749209403991699s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020093202590942383s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003757476806640625s
Believability | Calculation of trust value for SysMO-JERM took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-jerm took 2.6935877799987793s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2814805507659912s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 3.123283386230469e-05s
INFO | --- Analysis for bioportal-kisao took 2.725385904312134s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.029273986816406e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2728440761566162s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0002529621124267578s
Believability | Calculation of trust value for Loggerhead nesting took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-lhn took 2.749807834625244s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.27935194969177246s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0002009868621826172s
Believability | Calculation of trust value for Lipid Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-lipro took 2.7460243701934814s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.0531158447265625e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3371737003326416s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.001829385757446289s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-lnc took 3.2032532691955566s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 6.771087646484375e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2755742073059082s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006415843963623047s
Believability | Calculation of trust value for Mouse adult gross anatomy took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ma took 2.71588134765625s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.076957702636719e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2786436080932617s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0001957416534423828s
Believability | Calculation of trust value for Multiple alignment took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mao took 2.78910493850708s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.1961669921875e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2776212692260742s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020154476165771484s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0008218288421630859s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006787776947021484s
Believability | Calculation of trust value for Minimal anatomical terminology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mat took 2.694188117980957s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.506111145019531e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2736797332763672s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020210981369018555s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00042629241943359375s
Believability | Calculation of trust value for Breast tissue cell lines took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.6973633766174316s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2786545753479004s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020217418670654297s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007398128509521484s
Believability | Calculation of trust value for Cell line ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mccl took 2.7209677696228027s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2779514789581299s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014042854309082031s
Believability | Calculation of trust value for Cell line ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.7047390937805176s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.601478576660156e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.27654314041137695s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00023102760314941406s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mcv took 2.7262392044067383s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 3.981590270996094e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.27623939514160156s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020180225372314453s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00016260147094726562s
Believability | Calculation of trust value for Master Drug Data Base took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mddb took 2.7268226146698s
Availability | SPARQL endpoint availability check for MedDRA took 4.1961669921875e-05s
Availability | VoID file availability check for MedDRA took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2773916721343994s
Reputation | Calculation of the PageRank for MedDRA took 0.02001643180847168s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.001153707504272461s
Believability | Calculation of trust value for MedDRA took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mdr took 2.6790928840637207s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.00543212890625e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2857551574707031s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009315013885498047s
Believability | Calculation of trust value for MedlinePlus Health Topics took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.751314163208008s
Availability | SPARQL endpoint availability check for MeGO took 4.172325134277344e-05s
Availability | VoID file availability check for MeGO took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for MeGO took 0.274566650390625s
Reputation | Calculation of the PageRank for MeGO took 0.020093679428100586s
Interlinking | Calculation of Degree of Connection for MeGO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001392364501953125s
Believability | Calculation of trust value for MeGO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mego took 2.6916775703430176s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.124641418457031e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.32609987258911133s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018367767333984375s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.1498446464538574s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.276714563369751s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.02049994468688965s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0005962848663330078s
Believability | Calculation of trust value for Mental Functioning Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mf took 2.7536861896514893s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.076957702636719e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2765941619873047s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.000553131103515625s
Believability | Calculation of trust value for Medaka fish anatomy and development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mfo took 2.7499053478240967s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2802155017852783s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.021166324615478516s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0011017322540283203s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0010080337524414062s
Believability | Calculation of trust value for Emotion Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mfoem took 2.736492156982422s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 5.6743621826171875e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2742340564727783s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020835161209106445s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011730194091796875s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mhc took 2.744023561477661s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.100799560546875e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.27411842346191406s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020177602767944336s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006561279296875s
Believability | Calculation of trust value for Protein-protein interaction took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mi took 2.7185378074645996s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 5.078315734863281e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.27892303466796875s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007276535034179688s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-miro took 2.6884613037109375s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.27416348457336426s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.00091552734375s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00019359588623046875s
Believability | Calculation of trust value for Measurement Method Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mmo took 2.699723243713379s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for MGED Ontology took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.27321553230285645s
Reputation | Calculation of the PageRank for MGED Ontology took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003876686096191406s
Believability | Calculation of trust value for MGED Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mo took 2.669820785522461s
Availability | SPARQL endpoint availability check for Protein modification took 3.933906555175781e-05s
Availability | VoID file availability check for Protein modification took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2785637378692627s
Reputation | Calculation of the PageRank for Protein modification took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Protein modification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021314620971679688s
Believability | Calculation of trust value for Protein modification took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mod took 2.767681360244751s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.1484832763671875e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.27638912200927734s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006678104400634766s
Believability | Calculation of trust value for Mammalian phenotype took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mp took 2.741671562194824s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.553794860839844e-05s
Availability | VoID file availability check for Mouse pathology took 0.00031256675720214844s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.28406643867492676s
Reputation | Calculation of the PageRank for Mouse pathology took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004572868347167969s
Believability | Calculation of trust value for Mouse pathology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mpath took 2.6727712154388428s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.00543212890625e-05s
Availability | VoID file availability check for Mass spectrometry took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.27668309211730957s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02033400535583496s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003571510314941406s
Believability | Calculation of trust value for Mass spectrometry took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ms took 2.6848127841949463s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.100799560546875e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3271348476409912s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020273208618164062s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0019538402557373047s
Believability | Calculation of trust value for Medical Subject Headings took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-msh took 3.142199993133545s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.3392181396484375e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2793292999267578s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00019621849060058594s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mthch took 2.705167055130005s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.2771446704864502s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020243167877197266s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008013248443603516s
Believability | Calculation of trust value for Natural Products Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-natpro took 2.691042423248291s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.172325134277344e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2759888172149658s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008318424224853516s
Believability | Calculation of trust value for NCBI organismal classification took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.7329154014587402s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.00543212890625e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3292522430419922s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.001979827880859375s
Believability | Calculation of trust value for NCI Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ncit took 3.169884204864502s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.0531158447265625e-05s
Availability | VoID file availability check for National Drug Data File took 0.0009596347808837891s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.27628421783447266s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006096363067626953s
Believability | Calculation of trust value for National Drug Data File took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-nddf took 2.67649245262146s
Availability | SPARQL endpoint availability check for National Drug File took 4.0531158447265625e-05s
Availability | VoID file availability check for National Drug File took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for National Drug File took 0.27457690238952637s
Reputation | Calculation of the PageRank for National Drug File took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0008308887481689453s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012459754943847656s
Believability | Calculation of trust value for National Drug File took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.67825984954834s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.0531158447265625e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.27887511253356934s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011589527130126953s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.7589433193206787s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.27973294258117676s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006709098815917969s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-neomark took 2.7294983863830566s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2754201889038086s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001239776611328125s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.717304229736328s
Availability | SPARQL endpoint availability check for NIFSTD took 4.291534423828125e-05s
Availability | VoID file availability check for NIFSTD took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3247110843658447s
Reputation | Calculation of the PageRank for NIFSTD took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.002126455307006836s
Believability | Calculation of trust value for NIFSTD took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-nif took 3.16685152053833s
Availability | SPARQL endpoint availability check for NIF Cell took 4.029273986816406e-05s
Availability | VoID file availability check for NIF Cell took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.27439093589782715s
Reputation | Calculation of the PageRank for NIF Cell took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0015087127685546875s
Believability | Calculation of trust value for NIF Cell took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.7162697315216064s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.744529724121094e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0010306835174560547s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.27866673469543457s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.001416921615600586s
Believability | Calculation of trust value for NIF Dysfunction took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.705742120742798s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 6.0558319091796875e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2703735828399658s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005695819854736328s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nigo took 2.692838191986084s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.1484832763671875e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.27689099311828613s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005741119384765625s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nmr took 2.72112774848938s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2797541618347168s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.023186206817626953s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.000881195068359375s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00014257431030273438s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.743330955505371s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.26424479484558105s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02026987075805664s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012025833129882812s
Believability | Calculation of trust value for NanoParticle Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-npo took 2.6063292026519775s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2830824851989746s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007910728454589844s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-oae took 2.737074851989746s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.27256178855895996s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014891624450683594s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-obi took 2.697492837905884s
Availability | SPARQL endpoint availability check for OBOE took 4.1484832763671875e-05s
Availability | VoID file availability check for OBOE took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for OBOE took 0.2818183898925781s
Reputation | Calculation of the PageRank for OBOE took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for OBOE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010919570922851562s
Believability | Calculation of trust value for OBOE took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-oboe took 2.720993757247925s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.100799560546875e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.27423882484436035s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020107746124267578s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007851123809814453s
Believability | Calculation of trust value for OBOE SBC took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.7471110820770264s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.1484832763671875e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.28431057929992676s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005795955657958984s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ocre took 2.6992855072021484s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.00543212890625e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2788863182067871s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020114660263061523s
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.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0009105205535888672s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-odgi took 2.7102291584014893s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2798733711242676s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0009229183197021484s
Believability | Calculation of trust value for Ontology for Genetic Interval took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ogi took 2.7031259536743164s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.27605724334716797s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00029850006103515625s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 3.600120544433594e-05s
INFO | --- Analysis for bioportal-ogmd took 2.7236461639404297s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.27814722061157227s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006742477416992188s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ogms took 2.730712413787842s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.1484832763671875e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.27492475509643555s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011489391326904297s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-omim took 2.700890064239502s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.281724214553833s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0008826255798339844s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0004127025604248047s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omit took 2.6995832920074463s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 6.318092346191406e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.270552396774292s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020586013793945312s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006010532379150391s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omrse took 2.4829413890838623s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2792215347290039s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020707130432128906s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0009226799011230469s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0008893013000488281s
Believability | Calculation of trust value for Ontology of Data Mining took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ontodm took 2.6919634342193604s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.28093481063842773s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00024390220642089844s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ontodt took 2.7617104053497314s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 7.319450378417969e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.27402639389038086s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020142316818237305s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006124973297119141s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.710939884185791s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.649162292480469e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2762119770050049s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0010211467742919922s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0010371208190917969s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-opl took 2.700601100921631s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.0531158447265625e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.27202343940734863s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020194053649902344s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008947849273681641s
Believability | Calculation of trust value for Phenotypic quality took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pato took 2.6880156993865967s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.1484832763671875e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.28044581413269043s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008196830749511719s
Believability | Calculation of trust value for Physician Data Query took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-pdq took 2.7124385833740234s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.100799560546875e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2780013084411621s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.021225452423095703s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0009002685546875s
Believability | Calculation of trust value for Pediatric Terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pedterm took 2.681926727294922s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2784698009490967s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020328283309936523s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00021505355834960938s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-peo took 2.762301445007324s
Availability | SPARQL endpoint availability check for PHARE took 4.100799560546875e-05s
Availability | VoID file availability check for PHARE took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for PHARE took 0.2805054187774658s
Reputation | Calculation of the PageRank for PHARE took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006272792816162109s
Believability | Calculation of trust value for PHARE took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-phare took 2.726969003677368s
Availability | SPARQL endpoint availability check for PKO_Re took 4.291534423828125e-05s
Availability | VoID file availability check for PKO_Re took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.28078341484069824s
Reputation | Calculation of the PageRank for PKO_Re took 0.020190000534057617s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00016880035400390625s
Believability | Calculation of trust value for PKO_Re took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pko took 2.6949801445007324s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.27669644355773926s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0010173320770263672s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0010304450988769531s
Believability | Calculation of trust value for PMA 2010 took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-pma took 2.660106897354126s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 7.867813110351562e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.00032830238342285156s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2761406898498535s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001862049102783203s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pmr took 2.648529291152954s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2726600170135498s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.0207064151763916s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00039005279541015625s
Believability | Calculation of trust value for Plant Anatomy took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-po took 2.775712013244629s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.100799560546875e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2816133499145508s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020253896713256836s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.628036499023438e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.698843240737915s
Availability | SPARQL endpoint availability check for Plant Ontology took 6.151199340820312e-05s
Availability | VoID file availability check for Plant Ontology took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.2754964828491211s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00043463706970214844s
Believability | Calculation of trust value for Plant Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.7103514671325684s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.076957702636719e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2754981517791748s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006372928619384766s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pr took 2.722818613052368s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.076957702636719e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2773301601409912s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00025200843811035156s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-propreo took 2.7119603157043457s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Pathway ontology took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.2742588520050049s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012493133544921875s
Believability | Calculation of trust value for Pathway ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pw took 2.6655259132385254s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.27879834175109863s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020039796829223633s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-qibo took 2.6675565242767334s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.291534423828125e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3272254467010498s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017731189727783203s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-rcd took 3.144192934036255s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2734849452972412s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012969970703125s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-rctontology took 2.6838252544403076s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 6.29425048828125e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.27184391021728516s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.179115295410156e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-repo took 2.717665195465088s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.124641418457031e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0009303092956542969s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.26650071144104004s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0001842975616455078s
Believability | Calculation of trust value for Physico-chemical process took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rex took 2.680691719055176s
Availability | SPARQL endpoint availability check for RadLex took 4.1961669921875e-05s
Availability | VoID file availability check for RadLex took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for RadLex took 0.274777889251709s
Reputation | Calculation of the PageRank for RadLex took 0.020910263061523438s
Interlinking | Calculation of Degree of Connection for RadLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.001519918441772461s
Believability | Calculation of trust value for RadLex took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rid took 2.702986001968384s
Availability | SPARQL endpoint availability check for RNA ontology took 4.458427429199219e-05s
Availability | VoID file availability check for RNA ontology took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2685728073120117s
Reputation | Calculation of the PageRank for RNA ontology took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0006196498870849609s
Believability | Calculation of trust value for RNA ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rnao took 2.613407611846924s
Availability | SPARQL endpoint availability check for Role Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Role Ontology took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2709388732910156s
Reputation | Calculation of the PageRank for Role Ontology took 0.021555423736572266s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00022554397583007812s
Believability | Calculation of trust value for Role Ontology took 3.457069396972656e-05s
INFO | --- Analysis for bioportal-roleo took 2.7156195640563965s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.2750997543334961s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00018596649169921875s
Believability | Calculation of trust value for Rat Strain Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-rs took 2.6733670234680176s
Availability | SPARQL endpoint availability check for RxNORM took 4.1484832763671875e-05s
Availability | VoID file availability check for RxNORM took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2780730724334717s
Reputation | Calculation of the PageRank for RxNORM took 0.020934581756591797s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006239414215087891s
Believability | Calculation of trust value for RxNORM took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.6755177974700928s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.267692565917969e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2693004608154297s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.001041412353515625s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-sao took 2.699063301086426s
Availability | SPARQL endpoint availability check for Systems Biology took 8.296966552734375e-05s
Availability | VoID file availability check for Systems Biology took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.27521467208862305s
Reputation | Calculation of the PageRank for Systems Biology took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00044918060302734375s
Believability | Calculation of trust value for Systems Biology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sbo took 2.6954381465911865s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 5.0067901611328125e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.27425527572631836s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.0208890438079834s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010800361633300781s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sbro took 2.7395107746124268s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.27053093910217285s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013501644134521484s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sdo took 2.713458776473999s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.220008850097656e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2714109420776367s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003437995910644531s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sep took 2.708965301513672s
Availability | SPARQL endpoint availability check for Student Health Record took 3.981590270996094e-05s
Availability | VoID file availability check for Student Health Record took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2757441997528076s
Reputation | Calculation of the PageRank for Student Health Record took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004673004150390625s
Believability | Calculation of trust value for Student Health Record took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-shr took 2.681671380996704s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2791862487792969s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.001226663589477539s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sio took 3.4343714714050293s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.649162292480469e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.26844191551208496s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0001938343048095703s
Believability | Calculation of trust value for Situation-Based Access Control took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sitbac took 2.651191234588623s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 5.555152893066406e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.00048828125s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3240671157836914s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019567012786865234s
Believability | Calculation of trust value for SNOMED Clinical Terms took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-snomedct took 3.1842339038848877s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2819058895111084s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006639957427978516s
Believability | Calculation of trust value for SNP-Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-snpo took 2.7064719200134277s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.100799560546875e-05s
Availability | VoID file availability check for Sequence types and features took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.277097225189209s
Reputation | Calculation of the PageRank for Sequence types and features took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005619525909423828s
Believability | Calculation of trust value for Sequence types and features took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.7122550010681152s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 6.222724914550781e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.32261109352111816s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0016269683837890625s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sopharm took 3.2102034091949463s
Availability | SPARQL endpoint availability check for SoyOntology took 4.076957702636719e-05s
Availability | VoID file availability check for SoyOntology took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.2766742706298828s
Reputation | Calculation of the PageRank for SoyOntology took 0.020191669464111328s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0009288787841796875s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00014710426330566406s
Believability | Calculation of trust value for SoyOntology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-soy took 2.720991849899292s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Spider Ontology took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.27788877487182617s
Reputation | Calculation of the PageRank for Spider Ontology took 0.019950151443481445s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00030303001403808594s
Believability | Calculation of trust value for Spider Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-spd took 2.72452974319458s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2835707664489746s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020195722579956055s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002644062042236328s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-spto took 2.845245361328125s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.28044843673706055s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.0201108455657959s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004532337188720703s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sso took 2.7256648540496826s
Availability | SPARQL endpoint availability check for Software Ontology took 4.863739013671875e-05s
Availability | VoID file availability check for Software Ontology took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2834792137145996s
Reputation | Calculation of the PageRank for Software Ontology took 0.020058631896972656s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00040411949157714844s
Believability | Calculation of trust value for Software Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-swo took 2.7602076530456543s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2739286422729492s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02006816864013672s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023698806762695312s
Believability | Calculation of trust value for Tick gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tads took 2.655756711959839s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2792685031890869s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.019917726516723633s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008752346038818359s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tao took 2.7247586250305176s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.172325134277344e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.28016018867492676s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020029544830322266s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.559226989746094e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-taxrank took 2.6735329627990723s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.076957702636719e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0011327266693115234s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.2813258171081543s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020338058471679688s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 6.842613220214844e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-teddy took 2.7437703609466553s
Availability | SPARQL endpoint availability check for Time Event Ontology took 5.507469177246094e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.28420305252075195s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020086050033569336s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008323192596435547s
Believability | Calculation of trust value for Time Event Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teo took 2.7529876232147217s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 7.271766662597656e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2814061641693115s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020096540451049805s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00041174888610839844s
Believability | Calculation of trust value for Mosquito gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-tgma took 2.728459358215332s
Availability | SPARQL endpoint availability check for thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for thesaurus took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2803354263305664s
Reputation | Calculation of the PageRank for thesaurus took 0.020125627517700195s
Interlinking | Calculation of Degree of Connection for thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.365776062011719e-05s
Believability | Calculation of trust value for thesaurus took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.721529483795166s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.124641418457031e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.27508997917175293s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.01987481117248535s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003337860107421875s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.7227933406829834s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 5.7697296142578125e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.28113865852355957s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020240068435668945s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008294582366943359s
Believability | Calculation of trust value for Translational Medicine Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-tmo took 2.725017786026001s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2736637592315674s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020244836807250977s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.0001666545867919922s
Believability | Calculation of trust value for Plant Trait Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-to took 2.6936652660369873s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for TOK_Ontology took 0.000457763671875s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2798295021057129s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.0200650691986084s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001742839813232422s
Believability | Calculation of trust value for TOK_Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tok took 2.70326828956604s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.1961669921875e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2700686454772949s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00020074844360351562s
Believability | Calculation of trust value for Teleost taxonomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tto took 2.7071170806884766s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0012464523315429688s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2729530334472656s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.001020669937133789s
Believability | Calculation of trust value for Uber anatomy ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-uberon took 2.7255051136016846s
Availability | SPARQL endpoint availability check for Units Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Units Ontology took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.27815699577331543s
Reputation | Calculation of the PageRank for Units Ontology took 0.02114272117614746s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002276897430419922s
Believability | Calculation of trust value for Units Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.6901233196258545s
Availability | SPARQL endpoint availability check for Units of measurement took 5.817413330078125e-05s
Availability | VoID file availability check for Units of measurement took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2714204788208008s
Reputation | Calculation of the PageRank for Units of measurement took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00029778480529785156s
Believability | Calculation of trust value for Units of measurement took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-uo took 2.6791346073150635s
Availability | SPARQL endpoint availability check for VANDF took 4.172325134277344e-05s
Availability | VoID file availability check for VANDF took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for VANDF took 0.2727181911468506s
Reputation | Calculation of the PageRank for VANDF took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for VANDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006916522979736328s
Believability | Calculation of trust value for VANDF took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vandf took 2.7204606533050537s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2830207347869873s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020143985748291016s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004124641418457031s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vao took 2.7326738834381104s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 5.316734313964844e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.27761387825012207s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020087242126464844s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0005965232849121094s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-vhog took 2.74904203414917s
Availability | SPARQL endpoint availability check for VIVO took 4.8160552978515625e-05s
Availability | VoID file availability check for VIVO took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for VIVO took 0.27696728706359863s
Reputation | Calculation of the PageRank for VIVO took 0.020191192626953125s
Interlinking | Calculation of Degree of Connection for VIVO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003418922424316406s
Believability | Calculation of trust value for VIVO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vivo took 2.713728666305542s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0003819465637207031s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.26661014556884766s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020302534103393555s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012590885162353516s
Believability | Calculation of trust value for Vaccine Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-vo took 2.6783721446990967s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2701375484466553s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00019884109497070312s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vt took 2.668855667114258s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.100799560546875e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0007882118225097656s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2660481929779053s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004894733428955078s
Believability | Calculation of trust value for C. elegans gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-wbbt took 2.6428163051605225s
Availability | SPARQL endpoint availability check for C. elegans development took 4.124641418457031e-05s
Availability | VoID file availability check for C. elegans development took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2706022262573242s
Reputation | Calculation of the PageRank for C. elegans development took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.57763671875e-05s
Believability | Calculation of trust value for C. elegans development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-wbls took 2.697171926498413s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 5.459785461425781e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2772221565246582s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02020573616027832s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.940696716308594e-05s
Believability | Calculation of trust value for C. elegans phenotype took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.6719706058502197s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.506111145019531e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.27805352210998535s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.021703481674194336s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0010960102081298828s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0007269382476806641s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-who took 2.67448091506958s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.1484832763671875e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2775881290435791s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006692409515380859s
Believability | Calculation of trust value for Xenopus anatomy and development took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-xao took 2.7366268634796143s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0014684200286865234s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.28185224533081055s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023365020751953125s
Believability | Calculation of trust value for Experimental Conditions Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-xco took 2.7345149517059326s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.00543212890625e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2672126293182373s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00026869773864746094s
Believability | Calculation of trust value for Yeast phenotypes took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ypo took 2.6908137798309326s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 6.67572021484375e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2787625789642334s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007846355438232422s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-zfa took 2.7264068126678467s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.029273986816406e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0007905960083007812s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.27820467948913574s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020786762237548828s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.409385681152344e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 6.198883056640625e-06s
INFO | --- Analysis for Bioportal_link took 3.546504020690918s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4534766674041748s
Availability | VoID file availability check for BioSamples RDF took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2740471363067627s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020558595657348633s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.0013580322265625e-05s
INFO | --- Analysis for biosamples-rdf took 3.589574098587036s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.5396380424499512s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2731938362121582s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011682510375976562s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for bis-linked-data took 3.034569501876831s
Availability | SPARQL endpoint availability check for Bitzi took 4.00543212890625e-05s
Availability | VoID file availability check for Bitzi took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Bitzi took 0.2803947925567627s
Reputation | Calculation of the PageRank for Bitzi took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.075599670410156e-05s
Believability | Calculation of trust value for Bitzi took 8.58306884765625e-06s
INFO | --- Analysis for bitzi took 3.038161516189575s
Availability | SPARQL endpoint availability check for BizkaiSense took 3.9577484130859375e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2833080291748047s
Reputation | Calculation of the PageRank for BizkaiSense took 0.021014928817749023s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.457069396972656e-05s
Believability | Calculation of trust value for BizkaiSense took 7.3909759521484375e-06s
INFO | --- Analysis for bizkaisense took 3.027672290802002s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.0531158447265625e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2677953243255615s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.075599670410156e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.867813110351562e-06s
INFO | --- Analysis for blabla-itemlist took 3.0042836666107178s
Availability | SPARQL endpoint availability check for blabla.itemlist took 3.8623809814453125e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2776069641113281s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0994415283203125e-05s
Believability | Calculation of trust value for blabla.itemlist took 8.106231689453125e-06s
INFO | --- Analysis for blabla_itemlist took 3.0300164222717285s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 5.459785461425781e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0004100799560546875s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.27253270149230957s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020380735397338867s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0967254638671875e-05s
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.267692565917969e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for bll-thesaurus took 3.6900017261505127s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 0.519047737121582s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0004017353057861328s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.265916109085083s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.771087646484375e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for bluk-bnb took 12.151226043701172s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.3129696846008301s
Availability | VoID file availability check for Thesaurus BNCF took 0.00043082237243652344s
Extra | Recovery of all triples for Thesaurus BNCF took 54.53962564468384s
Performance | Total latancy measurement for Thesaurus BNCF took 0.7538316249847412s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6800222396850586s
Interoperability | New terms check for Thesaurus BNCF took 1.5257008075714111s
Versatility | Languages check for Thesaurus BNCF took 6.469354152679443s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8772299289703369s
Security | Check HTTPS for Thesaurus BNCF took 0.10040068626403809s
Interpretability | RDF structures check for Thesaurus BNCF took 0.14858770370483398s
Versatility | Serialization formats check for Thesaurus BNCF took 0.14428186416625977s
Availability | RDF dump link check for Thesaurus BNCF took 0.13997530937194824s
License | MR license check for Thesaurus BNCF took 0.14221620559692383s
License | HR license check for Thesaurus BNCF took 0.22223567962646484s
Amount of data | Number of property check for Thesaurus BNCF took 0.14051032066345215s
Understandability | Number of label check for Thesaurus BNCF took 0.2671518325805664s
Understandability | URI regex check for Thesaurus BNCF took 0.2817203998565674s
Understandability | Vocabs check for Thesaurus BNCF took 0.14226961135864258s
Verifiability | Authors check for Thesaurus BNCF took 0.14285731315612793s
Verifiability | Publishers check for Thesaurus BNCF took 0.14262843132019043s
Performance | Throughput check for Thesaurus BNCF took 10.749748706817627s
Amount of data | Check the number of entities for Thesaurus BNCF took 6.628036499023438e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.14632892608642578s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.14382100105285645s
Interlinking | skos check for Thesaurus BNCF took 0.21550536155700684s
Interlinking | skos check for Thesaurus BNCF took 0.17052555084228516s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.15202713012695312s
Currency | Creation date check for Thesaurus BNCF took 0.2911815643310547s
Currency | Modification date check for Thesaurus BNCF took 0.28703975677490234s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.819765329360962s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.14215874671936035s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.1908276081085205s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.14027142524719238s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.520747184753418s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5204575061798096s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.052574634552002s
Consistency | Disjoint class check for Thesaurus BNCF took 0.15314149856567383s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.9071600437164307s
Consistency | Misplaced classes for Thesaurus BNCF took 7.03057599067688s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.628454208374023s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.5378761291503906s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.2956254482269287s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.419205904006958s
Security | Sign check for Thesaurus BNCF took 0.1369178295135498s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.76987385749817s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3809657096862793s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.62939453125e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 5.7220458984375e-06s
INFO | --- Analysis for bncf-ns took 199.2298448085785s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5016458034515381s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006194114685058594s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.0672152042388916s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.673158884048462s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.277369499206543s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.225142478942871s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.34642291069031s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.7126588821411133s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2811903953552246s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3868229389190674s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4518458843231201s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.44254374504089355s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5681428909301758s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.24628686904907s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34311652183532715s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7552101612091064s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6538660526275635s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.41909074783325195s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4359147548675537s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33792614936828613s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.63886570930481s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.723403930664062e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3551619052886963s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3422689437866211s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.23361659049987793s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3481926918029785s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.41934657096862793s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6483452320098877s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.28353118896484375s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.00496745109558s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31871795654296875s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3567790985107422s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31026315689086914s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.043790340423584s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.023708343505859375s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028162002563476562s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33350539207458496s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.476804971694946s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4293558597564697s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3985955715179443s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.622446060180664s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.097429037094116s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.031093835830688477s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3667595386505127s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32219624519348145s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.162985801696777s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8667235374450684s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.021123886108398438s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.62939453125e-06s
INFO | --- Analysis for bpr took 383.83952951431274s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.363059997558594e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.7093985080718994s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.651878356933594e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.0067901611328125e-06s
INFO | --- Analysis for brazilian-politicians took 5.777095079421997s
Availability | SPARQL endpoint availability check for BrazilianCities took 3.933906555175781e-05s
Availability | VoID file availability check for BrazilianCities took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.2865285873413086s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020145416259765625s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.0040740966796875e-05s
Believability | Calculation of trust value for BrazilianCities took 6.198883056640625e-06s
INFO | --- Analysis for braziliancities took 3.474677562713623s
Availability | SPARQL endpoint availability check for Bricklink took 1.6054422855377197s
Availability | VoID file availability check for Bricklink took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for Bricklink took 0.27927684783935547s
Reputation | Calculation of the PageRank for Bricklink took 0.0203096866607666s
Interlinking | Calculation of Degree of Connection for Bricklink took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bricklink took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.198883056640625e-05s
Believability | Calculation of trust value for Bricklink took 6.198883056640625e-06s
INFO | --- Analysis for bricklink took 11.220078229904175s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.308659315109253s
Availability | VoID file availability check for British Museum Collection took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.27930450439453125s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.361701965332031e-05s
Believability | Calculation of trust value for British Museum Collection took 9.059906005859375e-06s
INFO | --- Analysis for british-museum-collection took 73.76560473442078s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.267692565917969e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.27505064010620117s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020555734634399414s
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.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.029273986816406e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 8.821487426757812e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.987678050994873s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.076957702636719e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2747523784637451s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 3.0279159545898438e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.867813110351562e-06s
INFO | --- Analysis for bsv took 3.9133713245391846s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.838489294052124s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.7353241443634033s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.430511474609375e-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.6559813022613525s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.100799560546875e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.2799067497253418s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.02021050453186035s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.314018249511719e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 6.198883056640625e-06s
INFO | --- Analysis for bund-offener-haushalt took 3.0527448654174805s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.076957702636719e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.2706418037414551s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.123283386230469e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 6.9141387939453125e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 3.0328474044799805s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.20542383193969727s
Availability | VoID file availability check for business.data.gov.uk took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2767677307128906s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.030632019042969e-05s
Believability | Calculation of trust value for business.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for business-data-gov-uk took 2.8499505519866943s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.49248290061950684s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0013811588287353516s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.4769103527069092s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.6153936386108398s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.42679691314697266s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7208459377288818s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 30.217550039291382s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.457442045211792s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.13547825813293457s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.7196733951568604s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.27895474433898926s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3614785671234131s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.42957162857055664s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.477900981903076s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3146936893463135s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.43355226516723633s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6738545894622803s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.2889242172241211s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.36263585090637207s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3905806541442871s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.200241088867188e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.23243999481201172s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.2549264430999756s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.26964282989501953s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.2578604221343994s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.23035001754760742s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.461169958114624s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.4598095417022705s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 0.5044054985046387s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.15938472747802734s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.03377938270568848s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.1395246982574463s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 0.13432621955871582s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 1.4829585552215576s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03271985054016113s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.13479185104370117s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 5.384066581726074s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.2784121036529541s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.019699573516845703s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 7.867813110351562e-06s
INFO | --- Analysis for BVMC took 93.54108715057373s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.076957702636719e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.2845606803894043s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.019862890243530273s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.3855438232421875e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 8.58306884765625e-06s
INFO | --- Analysis for cabbage took 3.054767370223999s
Availability | SPARQL endpoint availability check for cablegate took 1.7847623825073242s
Availability | VoID file availability check for cablegate took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for cablegate took 0.2798483371734619s
Reputation | Calculation of the PageRank for cablegate took 0.02027726173400879s
Interlinking | Calculation of Degree of Connection for cablegate took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.2479248046875e-05s
Believability | Calculation of trust value for cablegate took 8.106231689453125e-06s
INFO | --- Analysis for cablegate took 17.65390157699585s
Availability | SPARQL endpoint availability check for Calames took 4.1484832763671875e-05s
Availability | VoID file availability check for Calames took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Calames took 0.27744150161743164s
Reputation | Calculation of the PageRank for Calames took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for Calames took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Calames took 3.5762786865234375e-05s
Believability | Calculation of trust value for Calames took 8.106231689453125e-06s
INFO | --- Analysis for calames took 4.404894590377808s
Availability | SPARQL endpoint availability check for CaLiGraph took 15.935664653778076s
Availability | VoID file availability check for CaLiGraph took 0.0002696514129638672s
Extra | Recovery of all triples for CaLiGraph took 32.943045139312744s
Performance | Total latancy measurement for CaLiGraph took 53.893404960632324s
Amount of data | Number of triples check for CaLiGraph took 12.281055450439453s
Interoperability | New terms check for CaLiGraph took 2.1023459434509277s
Versatility | Languages check for CaLiGraph took 60.319523334503174s
Interpretability | Number of blank nodes check for CaLiGraph took 0.24748921394348145s
Security | Check HTTPS for CaLiGraph took 0.1300647258758545s
Interpretability | RDF structures check for CaLiGraph took 0.29442310333251953s
Versatility | Serialization formats check for CaLiGraph took 0.3317291736602783s
Availability | RDF dump link check for CaLiGraph took 0.296649694442749s
License | MR license check for CaLiGraph took 0.47124719619750977s
License | HR license check for CaLiGraph took 60.30419135093689s
Amount of data | Number of property check for CaLiGraph took 0.25182580947875977s
Understandability | Number of label check for CaLiGraph took 3.3737945556640625s
Understandability | URI regex check for CaLiGraph took 0.5494480133056641s
Understandability | Vocabs check for CaLiGraph took 0.28216052055358887s
Verifiability | Authors check for CaLiGraph took 0.29688072204589844s
Verifiability | Publishers check for CaLiGraph took 0.2446918487548828s
Performance | Throughput check for CaLiGraph took 11.499988794326782s
Amount of data | Check the number of entities for CaLiGraph took 0.014898300170898438s
Verifiability | Contribs. check for CaLiGraph took 0.2682631015777588s
Interlinking | sameAs chians check for CaLiGraph took 0.6589820384979248s
Interlinking | skos check for CaLiGraph took 0.4011828899383545s
Interlinking | skos check for CaLiGraph took 0.2209031581878662s
Timeliness | dataset update frequency check for CaLiGraph took 0.31667399406433105s
Currency | Creation date check for CaLiGraph took 0.5324270725250244s
Currency | Modification date check for CaLiGraph took 0.4989798069000244s
Rep.Conc. | URIs length for CaLiGraph took 61.1102557182312s
Interoperability | New vocabularies check for CaLiGraph took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.247481107711792s
Accuracy | Check Functional Property for CaLiGraph took 0.28283238410949707s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2879211902618408s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6206941604614258s
Accuracy | Check White space in annotation for CaLiGraph took 0.02634572982788086s
Accuracy | Check Datatype consistency for CaLiGraph took 0.052247047424316406s
Consistency | Disjoint class check for CaLiGraph took 0.24904084205627441s
Consistency | Check Misplaced properties for CaLiGraph took 61.01590895652771s
Consistency | Misplaced classes for CaLiGraph took 18.839889526367188s
Consistency | Check Ontology hijacking for CaLiGraph took 4.582944631576538s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.347395896911621s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 73.92669177055359s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03606414794921875s
Conciseness | Check Intensional conciseness for CaLiGraph took 19.740009784698486s
Security | Sign check for CaLiGraph took 8.90176272392273s
Availability | Check URIs Dereferenciability for CaLiGraph took 5.404475927352905s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.7460620403289795s
Reputation | Calculation of the PageRank for CaLiGraph took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.0994415283203125e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 7.3909759521484375e-06s
INFO | --- Analysis for CaLiGraph took 6881.167071342468s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.24600744247436523s
Availability | VoID file availability check for CaLiGraph took 0.0006182193756103516s
Extra | Recovery of all triples for CaLiGraph took 2.3334195613861084s
Performance | Total latancy measurement for CaLiGraph took 1.1600806713104248s
Amount of data | Number of triples check for CaLiGraph took 11.76075029373169s
Interoperability | New terms check for CaLiGraph took 2.1454174518585205s
Versatility | Languages check for CaLiGraph took 60.35454344749451s
Interpretability | Number of blank nodes check for CaLiGraph took 0.24789690971374512s
Security | Check HTTPS for CaLiGraph took 0.13303804397583008s
Interpretability | RDF structures check for CaLiGraph took 0.2559525966644287s
Versatility | Serialization formats check for CaLiGraph took 0.2794973850250244s
Availability | RDF dump link check for CaLiGraph took 0.2773609161376953s
License | MR license check for CaLiGraph took 0.29217028617858887s
License | HR license check for CaLiGraph took 60.29985165596008s
Amount of data | Number of property check for CaLiGraph took 0.25690507888793945s
Understandability | Number of label check for CaLiGraph took 3.0553667545318604s
Understandability | URI regex check for CaLiGraph took 0.5277717113494873s
Understandability | Vocabs check for CaLiGraph took 0.24928927421569824s
Verifiability | Authors check for CaLiGraph took 0.2521824836730957s
Verifiability | Publishers check for CaLiGraph took 0.24800586700439453s
Amount of data | Check the number of entities for CaLiGraph took 0.014813423156738281s
Verifiability | Contribs. check for CaLiGraph took 0.2590820789337158s
Interlinking | sameAs chians check for CaLiGraph took 0.6239962577819824s
Interlinking | skos check for CaLiGraph took 0.2589418888092041s
Interlinking | skos check for CaLiGraph took 0.21532225608825684s
Timeliness | dataset update frequency check for CaLiGraph took 0.25328564643859863s
Currency | Creation date check for CaLiGraph took 0.5116076469421387s
Currency | Modification date check for CaLiGraph took 0.4982028007507324s
Rep.Conc. | URIs length for CaLiGraph took 61.09295678138733s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.24599742889404297s
Accuracy | Check Functional Property for CaLiGraph took 0.24504995346069336s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2540910243988037s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6070537567138672s
Accuracy | Check White space in annotation for CaLiGraph took 0.0265347957611084s
Accuracy | Check Datatype consistency for CaLiGraph took 0.051740407943725586s
Consistency | Disjoint class check for CaLiGraph took 0.2482142448425293s
Consistency | Check Misplaced properties for CaLiGraph took 61.01273822784424s
Consistency | Misplaced classes for CaLiGraph took 0.5653231143951416s
Consistency | Check Ontology hijacking for CaLiGraph took 2.166579484939575s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.4130642414093018s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.638065338134766s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029494047164916992s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4824256896972656s
Security | Sign check for CaLiGraph took 0.2801380157470703s
Availability | Check URIs Dereferenciability for CaLiGraph took 22.387847423553467s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.7950456142425537s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 8.034706115722656e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 7.152557373046875e-06s
INFO | --- Analysis for caligraph took 2884.516451358795s
Availability | SPARQL endpoint availability check for can-link took 4.5299530029296875e-05s
Availability | VoID file availability check for can-link took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for can-link took 0.286301851272583s
Reputation | Calculation of the PageRank for can-link took 0.020203351974487305s
Interlinking | Calculation of Degree of Connection for can-link took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for can-link took 3.314018249511719e-05s
Believability | Calculation of trust value for can-link took 7.867813110351562e-06s
INFO | --- Analysis for can-link took 5.271450996398926s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.08105611801147461s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.27468109130859375s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.001049041748046875s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.790855407714844e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.867813110351562e-06s
INFO | --- Analysis for cap-italy-rdf took 3.965991258621216s
Availability | SPARQL endpoint availability check for person took 4.410743713378906e-05s
Availability | VoID file availability check for person took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for person took 0.2761876583099365s
Reputation | Calculation of the PageRank for person took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for person took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for person took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for person took 3.0279159545898438e-05s
Believability | Calculation of trust value for person took 8.821487426757812e-06s
INFO | --- Analysis for card took 3.3750112056732178s
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.0006341934204101562s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.27427124977111816s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020870208740234375s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0010640621185302734s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.482269287109375e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 7.867813110351562e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.1430251598358154s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.029273986816406e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.27574896812438965s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 2.9802322387695312e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.867813110351562e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 3.5671892166137695s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.5332005023956299s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00026154518127441406s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 126.19393396377563s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 1.0069842338562012s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 8.144386053085327s
Interoperability | New terms check for Norway catch records dataset @PSNC took 13.9733304977417s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.1966083049774s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.8644931316375732s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.26747918128967285s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 10.907661199569702s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.26528048515319824s
License | MR license check for Norway catch records dataset @PSNC took 0.467318058013916s
License | HR license check for Norway catch records dataset @PSNC took 300.16482496261597s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.2639734745025635s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.390172243118286s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.780759334564209s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.32008838653564453s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.19909882545471191s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.2657432556152344s
Performance | Throughput check for Norway catch records dataset @PSNC took 10.137087106704712s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.700920104980469e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.2066957950592041s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.20527243614196777s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4533958435058594s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.45671963691711426s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 5.796739101409912s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.4976377487182617s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.2391340732574463s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 149.41267228126526s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.2069377899169922s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.3505699634552002s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.354036808013916s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 40.95578742027283s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.69783616065979s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.6101126670837402s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.21232962608337402s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 80.71207666397095s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.459607124328613s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 39.47783041000366s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.4318666458129883s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 84.26093602180481s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.7367069721221924s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5818288326263428s
Security | Sign check for Norway catch records dataset @PSNC took 0.6254441738128662s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 18.467280864715576s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 1.2871088981628418s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02099895477294922s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 9.989738464355469e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 9.775161743164062e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2292.9692385196686s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.506111145019531e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2786433696746826s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010037422180175781s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 6.9141387939453125e-06s
INFO | --- Analysis for ce4r took 6.717092037200928s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35646605491638184s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002562999725341797s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.5948874950408936s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7944841384887695s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3237731456756592s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.8104820251464844s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.13288497924805s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16334748268127441s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4171602725982666s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21975207328796387s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22585797309875488s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28040194511413574s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39902353286743164s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2608063220977783s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.36225008964538574s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3013434410095215s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15231871604919434s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28601694107055664s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19815635681152344s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.514358758926392s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 0.00011491775512695312s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2019965648651123s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1917591094970703s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26567506790161133s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1457521915435791s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2066183090209961s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3998126983642578s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.38210225105285645s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.123835563659668s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15536856651306152s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.16555118560791016s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.20832109451293945s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6300413608551025s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.0276491641998291s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028457164764404297s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1836566925048828s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2856667041778564s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.216015577316284s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.4018363952636719s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5973570346832275s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03260540962219238s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.19635891914367676s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1492767333984375s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 1836.9910407066345s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.1690125465393066s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.2636184692382812e-05s
INFO | --- Analysis for ceo took 1961.969714641571s
Availability | SPARQL endpoint availability check for Charging Stations took 4.172325134277344e-05s
Availability | VoID file availability check for Charging Stations took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.27312588691711426s
Reputation | Calculation of the PageRank for Charging Stations took 0.019799232482910156s
Interlinking | Calculation of Degree of Connection for Charging Stations took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Charging Stations took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.147125244140625e-05s
Believability | Calculation of trust value for Charging Stations took 7.62939453125e-06s
INFO | --- Analysis for charging-stations took 3.890021324157715s
Availability | SPARQL endpoint availability check for Chat Game corpus took 7.581710815429688e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.27382540702819824s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02026677131652832s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.600120544433594e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.6689300537109375e-05s
INFO | --- Analysis for chat-game-corpus took 13.946101188659668s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 6.723403930664062e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.2739260196685791s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.019971847534179688s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.170967102050781e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 8.344650268554688e-06s
INFO | --- Analysis for chebi took 3.409517526626587s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.839897155761719e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0010166168212890625s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.71478271484375s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.023422956466674805s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.175041198730469e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 6.198883056640625e-06s
INFO | --- Analysis for chem2bio2rdf took 137.97891211509705s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.823763370513916s
Availability | VoID file availability check for ChEMBL RDF took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.2819540500640869s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.982948303222656e-05s
Believability | Calculation of trust value for ChEMBL RDF took 8.106231689453125e-06s
INFO | --- Analysis for chembl-rdf took 4.0542073249816895s
Availability | SPARQL endpoint availability check for chemdb  dataset took 123.02281665802002s
Availability | VoID file availability check for chemdb  dataset took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.27809810638427734s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 6.270408630371094e-05s
Believability | Calculation of trust value for chemdb  dataset took 7.3909759521484375e-06s
INFO | --- Analysis for chemdb-basicInfo took 258.434246301651s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 142.9591579437256s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.7075803279876709s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02080059051513672s
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.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 0.00010991096496582031s
Believability | Calculation of trust value for chemdb estimated properties dataset took 7.867813110351562e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 277.4129886627197s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 142.56357169151306s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.278395414352417s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.601478576660156e-05s
Believability | Calculation of trust value for chemdb phase transition dataset took 8.106231689453125e-06s
INFO | --- Analysis for chemdb-phaseTransition took 277.9521131515503s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 142.60710167884827s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.7655446529388428s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 7.033348083496094e-05s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 5.9604644775390625e-06s
INFO | --- Analysis for chemdb-thermochemistry took 277.2412896156311s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.291534423828125e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.7047011852264404s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.021700143814086914s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0010333061218261719s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 8.344650268554688e-06s
INFO | --- Analysis for chempedia-rdf took 11.858174562454224s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.2438507080078125e-05s
Availability | VoID file availability check for Chiman Maru took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.7087147235870361s
Reputation | Calculation of the PageRank for Chiman Maru took 0.0202176570892334s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.170967102050781e-05s
Believability | Calculation of trust value for Chiman Maru took 7.152557373046875e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 4.168490886688232s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.4721224308014s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.9172430038452148s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.0221710205078125s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0010025501251220703s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.124641418457031e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.62939453125e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 800.006175994873s
Availability | SPARQL endpoint availability check for Chronicling America took 4.482269287109375e-05s
Availability | VoID file availability check for Chronicling America took 0.0003604888916015625s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.2680337429046631s
Reputation | Calculation of the PageRank for Chronicling America took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for Chronicling America took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010037422180175781s
Believability | Calculation of trust value for Chronicling America took 7.867813110351562e-06s
INFO | --- Analysis for chronicling-america took 8.353545904159546s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.667586088180542s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.00036525726318359375s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 133.11079716682434s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.579275369644165s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.7056424617767334s
Interoperability | New terms check for Cultural Heritage Thesaurus took 1.8381688594818115s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.5026652812957764s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.6128582954406738s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.31983447074890137s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3080112934112549s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 0.3246591091156006s
License | MR license check for Cultural Heritage Thesaurus took 0.29297399520874023s
License | HR license check for Cultural Heritage Thesaurus took 0.39228129386901855s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.325758695602417s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3275721073150635s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5763218402862549s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3146820068359375s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.312716007232666s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.30080485343933105s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.366372346878052s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 6.937980651855469e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2867758274078369s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.2842903137207031s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3283259868621826s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.2977635860443115s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.28328537940979004s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6628656387329102s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6386520862579346s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 13.865440368652344s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.2913358211517334s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.29743075370788574s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2953338623046875s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.601579189300537s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22467494010925293s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.2993128299713135s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.1871459484100342s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.333263635635376s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.713600397109985s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.454633951187134s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001595020294189453s
Security | Sign check for Cultural Heritage Thesaurus took 0.3283717632293701s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 334.6219570636749s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.9093658924102783s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.08054018020629883s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00010728836059570312s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 1.1920928955078125e-06s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for cht took 548.9142537117004s
Availability | SPARQL endpoint availability check for ciard-ring took 9.107589721679688e-05s
Availability | VoID file availability check for ciard-ring took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2730743885040283s
Reputation | Calculation of the PageRank for ciard-ring took 0.057025909423828125s
Interlinking | Calculation of Degree of Connection for ciard-ring took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.482269287109375e-05s
Believability | Calculation of trust value for ciard-ring took 6.198883056640625e-06s
INFO | --- Analysis for ciard-ring took 3.1256792545318604s
Availability | SPARQL endpoint availability check for Cine Figure took 4.172325134277344e-05s
Availability | VoID file availability check for Cine Figure took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2714414596557617s
Reputation | Calculation of the PageRank for Cine Figure took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Cine Figure took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cine Figure took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.458427429199219e-05s
Believability | Calculation of trust value for Cine Figure took 7.152557373046875e-06s
INFO | --- Analysis for Cine_Figure took 2.932164192199707s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.77584719657898s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0008432865142822266s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.718801736831665s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.078315734863281e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 175.89303278923035s
Availability | SPARQL endpoint availability check for CIPFA took 4.267692565917969e-05s
Availability | VoID file availability check for CIPFA took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2818021774291992s
Reputation | Calculation of the PageRank for CIPFA took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for CIPFA took 4.863739013671875e-05s
Believability | Calculation of trust value for CIPFA took 5.0067901611328125e-06s
INFO | --- Analysis for cipfa took 2.830082654953003s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 0.2733423709869385s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.26765012741088867s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00038909912109375s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 8.821487426757812e-06s
INFO | --- Analysis for ckan took 3.4029581546783447s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5983738899230957s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.276181697845459s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for CLaSSES took 4.108186483383179s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.100799560546875e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2769923210144043s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02028512954711914s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.1948089599609375e-05s
Believability | Calculation of trust value for Temples of the Classical World took 6.67572021484375e-06s
INFO | --- Analysis for classical_temples took 3.653172492980957s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.977808952331543s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2872617244720459s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0008478164672851562s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 9.679794311523438e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 5.7220458984375e-06s
INFO | --- Analysis for clean-energy-data-reegle took 8.940116167068481s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.100799560546875e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2764170169830322s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.510185241699219e-05s
Believability | Calculation of trust value for CLLD-afbo took 7.867813110351562e-06s
INFO | --- Analysis for clld-afbo took 3.555067539215088s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.0531158447265625e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.27646780014038086s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020154237747192383s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.843971252441406e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.239776611328125e-05s
INFO | --- Analysis for clld-apics took 3.8108952045440674s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.1484832763671875e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2800307273864746s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020355701446533203s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.647804260253906e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 8.106231689453125e-06s
INFO | --- Analysis for clld-ewave took 3.5654232501983643s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2755608558654785s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.021191835403442383s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010251998901367188s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 7.62939453125e-06s
INFO | --- Analysis for clld-glottolog took 3.586406946182251s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.076957702636719e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.282179594039917s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.987022399902344e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 7.62939453125e-06s
INFO | --- Analysis for clld-phoible took 3.592909336090088s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.220008850097656e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.2677276134490967s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.534027099609375e-05s
Believability | Calculation of trust value for CLLD-SAILS took 6.198883056640625e-06s
INFO | --- Analysis for clld-sails took 3.76833176612854s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.00543212890625e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.28279566764831543s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 9.131431579589844e-05s
Believability | Calculation of trust value for CLLD-WALS took 5.4836273193359375e-06s
INFO | --- Analysis for clld-wals took 3.7133350372314453s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 7.724761962890625e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.33748888969421387s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02080988883972168s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.700920104980469e-05s
Believability | Calculation of trust value for CLLD-WOLD took 8.106231689453125e-06s
INFO | --- Analysis for clld-wold took 4.142815113067627s
Availability | SPARQL endpoint availability check for COD inventory took 3.910064697265625e-05s
Availability | VoID file availability check for COD inventory took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for COD inventory took 0.2759287357330322s
Reputation | Calculation of the PageRank for COD inventory took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.3855438232421875e-05s
Believability | Calculation of trust value for COD inventory took 6.9141387939453125e-06s
INFO | --- Analysis for cod-inventory took 2.9973158836364746s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.13185358047485352s
Availability | VoID file availability check for Cooperation Databank took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.27649784088134766s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.62396240234375e-05s
Believability | Calculation of trust value for Cooperation Databank took 7.152557373046875e-06s
INFO | --- Analysis for CoDa took 2.6294424533843994s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.124641418457031e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.27614593505859375s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.2901763916015625e-05s
Believability | Calculation of trust value for CODE Endpoint took 7.867813110351562e-06s
INFO | --- Analysis for code-endpoint took 3.0061728954315186s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.5138082504272461s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.26758790016174316s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.245208740234375e-06s
INFO | --- Analysis for coins-openuplabs took 3.0021567344665527s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 2.762585163116455s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.26568174362182617s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 7.891654968261719e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 6.9141387939453125e-06s
INFO | --- Analysis for CoLChina_sp2000 took 6.644697904586792s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.05334210395812988s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.26486706733703613s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020173311233520508s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.6716461181640625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for colinda took 2.5703041553497314s
Availability | SPARQL endpoint availability check for CN  2012 took 27.533698320388794s
Availability | VoID file availability check for CN  2012 took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.31250977516174316s
Reputation | Calculation of the PageRank for CN  2012 took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for CN  2012 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CN  2012 took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.337860107421875e-05s
Believability | Calculation of trust value for CN  2012 took 5.0067901611328125e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 128.68946623802185s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.029273986816406e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.2736949920654297s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020248889923095703s
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.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 6.67572021484375e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 3.0236971378326416s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.076957702636719e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2795872688293457s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 2.86102294921875e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.3909759521484375e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 3.021615982055664s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.00543212890625e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.27457714080810547s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 2.8371810913085938e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 6.9141387939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.991611957550049s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.267692565917969e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.27178311347961426s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020040273666381836s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.765655517578125e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 1.9311904907226562e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 3.0181217193603516s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 5.221366882324219e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.2767140865325928s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02019643783569336s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 2.765655517578125e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 6.9141387939453125e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 3.019815444946289s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.43283677101135254s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.27592015266418457s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for CompHistSem took 3.9039950370788574s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 28.905736684799194s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2782115936279297s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.0531158447265625e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 6.4373016357421875e-06s
INFO | --- Analysis for comsode-d3-2 took 103.10375761985779s
Availability | SPARQL endpoint availability check for ConceptNet took 3.981590270996094e-05s
Availability | VoID file availability check for ConceptNet took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.27838587760925293s
Reputation | Calculation of the PageRank for ConceptNet took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for ConceptNet took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.6464462280273438e-05s
Believability | Calculation of trust value for ConceptNet took 6.9141387939453125e-06s
INFO | --- Analysis for conceptnet took 3.0281612873077393s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.076957702636719e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2802088260650635s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.392333984375e-05s
Believability | Calculation of trust value for 2011 US Congress People took 5.0067901611328125e-06s
INFO | --- Analysis for congresspeople took 3.098540782928467s
Availability | SPARQL endpoint availability check for MIMO took 0.2861959934234619s
Availability | VoID file availability check for MIMO took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for MIMO took 0.2784080505371094s
Reputation | Calculation of the PageRank for MIMO took 0.020221471786499023s
Interlinking | Calculation of Degree of Connection for MIMO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.0967254638671875e-05s
Believability | Calculation of trust value for MIMO took 9.059906005859375e-06s
INFO | --- Analysis for CONNECTED took 4.18927788734436s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 3.933906555175781e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2833108901977539s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020137786865234375s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.7179718017578125e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 3.074517250061035s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.00543212890625e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.27225399017333984s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.6941299438476562e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 7.62939453125e-06s
INFO | --- Analysis for copac-library-catalogue took 3.035501480102539s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.124641418457031e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.27602553367614746s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.7418136596679688e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.9141387939453125e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.4955713748931885s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.1961669921875e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.36672329902648926s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.985664367675781e-05s
Believability | Calculation of trust value for CopyrightTermBank took 6.9141387939453125e-06s
INFO | --- Analysis for copyrighttermbank took 34.210878133773804s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.3230504989624023s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2890207767486572s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.361701965332031e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 6.9141387939453125e-06s
INFO | --- Analysis for core took 7.600570201873779s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.4593327045440674s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002574920654296875s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 122.962233543396s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 1.0837786197662354s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 8.326778173446655s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.85607361793518s
Versatility | Languages check for Corine linked dataset @PSNC took 300.1887195110321s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.9541213512420654s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.24666905403137207s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 10.322162866592407s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.3039531707763672s
License | MR license check for Corine linked dataset @PSNC took 0.5122313499450684s
License | HR license check for Corine linked dataset @PSNC took 300.20512318611145s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.2645609378814697s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.4619767665863037s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.8720383644104004s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.4557218551635742s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.2074902057647705s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.26544904708862305s
Performance | Throughput check for Corine linked dataset @PSNC took 10.127915859222412s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 6.699562072753906e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.20299816131591797s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.20528650283813477s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4571716785430908s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4531288146972656s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.7071897983551025s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5052909851074219s
Currency | Modification date check for Corine linked dataset @PSNC took 0.23088622093200684s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 159.35422110557556s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.20258450508117676s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.28139281272888184s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.2933509349822998s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 41.017176389694214s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.7131507396698s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.633232355117798s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.20390725135803223s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 83.1875581741333s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.592739820480347s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 42.93337941169739s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.4562153816223145s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 84.29539036750793s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.7831203937530518s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.6317861080169678s
Security | Sign check for Corine linked dataset @PSNC took 0.8152260780334473s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 5.4803993701934814s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.724358081817627s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.02109551429748535s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 4.5299530029296875e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Corine_linked_dataset took 2290.8579461574554s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.2438507080078125e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.7040143013000488s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0010097026824951172s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.363059997558594e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.58306884765625e-06s
INFO | --- Analysis for corn took 6.541419267654419s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 7.963180541992188e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.28058290481567383s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020289182662963867s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.1948089599609375e-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 4.745723724365234s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.886222839355469e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.7098290920257568s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020876169204711914s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.0279159545898438e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 5.9604644775390625e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 3.879533052444458s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 7.867813110351562e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0009355545043945312s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.27536845207214355s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 7.963180541992188e-05s
Believability | Calculation of trust value for Cornetto1.2 took 8.106231689453125e-06s
INFO | --- Analysis for cornetto took 34.96895170211792s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.16630935668945312s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0006475448608398438s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 101.20389461517334s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5967628955841064s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 89.46846556663513s
Interoperability | New terms check for Corporate Body Named Authority List  took 112.48896646499634s
Versatility | Languages check for Corporate Body Named Authority List  took 300.12256956100464s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 1.3846242427825928s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.33457326889038086s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.6844797134399414s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 5.646013498306274s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.29370594024658203s
License | MR license check for Corporate Body Named Authority List  took 0.27856945991516113s
License | HR license check for Corporate Body Named Authority List  took 300.1047396659851s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.1858210563659668s
Understandability | Number of label check for Corporate Body Named Authority List  took 6.671935081481934s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.24267148971557617s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.10172390937805176s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.1501026153564453s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2436976432800293s
Performance | Throughput check for Corporate Body Named Authority List  took 10.747264385223389s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.104873657226562e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.25446033477783203s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 10.855490922927856s
Interlinking | skos check for Corporate Body Named Authority List  took 0.2657337188720703s
Interlinking | skos check for Corporate Body Named Authority List  took 0.383591890335083s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.311260461807251s
Currency | Creation date check for Corporate Body Named Authority List  took 0.28966546058654785s
Currency | Modification date check for Corporate Body Named Authority List  took 0.2360825538635254s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 470.3508565425873s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.18284916877746582s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.18438005447387695s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.19222402572631836s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 31.506359815597534s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.095268487930298s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6024794578552246s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.1383345127105713s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4434425830841s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.421201705932617s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 50.106382608413696s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.5595123767852783s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.46601700782776s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.9834659099578857s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.5530319213867188s
Security | Sign check for Corporate Body Named Authority List  took 0.147385835647583s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 4.123667240142822s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.569352149963379s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02132868766784668s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 0.00011372566223144531s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 7.867813110351562e-06s
INFO | --- Analysis for corporate-body took 15436.944862604141s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5396125316619873s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.708554744720459s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020339250564575195s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for CorpusFibonacci took 5.2738938331604s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 3.9577484130859375e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.27796411514282227s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020128250122070312s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for corscheck took 3.46396541595459s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.14023470878601074s
Availability | VoID file availability check for Country Name Authority List took 0.0007061958312988281s
Extra | Recovery of all triples for Country Name Authority List took 113.5892882347107s
Performance | Total latancy measurement for Country Name Authority List took 0.611508846282959s
Amount of data | Number of triples check for Country Name Authority List took 89.08514404296875s
Interoperability | New terms check for Country Name Authority List took 96.60835599899292s
Versatility | Languages check for Country Name Authority List took 300.1231334209442s
Interpretability | Number of blank nodes check for Country Name Authority List took 1.5939464569091797s
Security | Check HTTPS for Country Name Authority List took 0.21522116661071777s
Interpretability | RDF structures check for Country Name Authority List took 0.44907116889953613s
Versatility | Serialization formats check for Country Name Authority List took 3.8023884296417236s
Availability | RDF dump link check for Country Name Authority List took 0.27218103408813477s
License | MR license check for Country Name Authority List took 0.2528533935546875s
License | HR license check for Country Name Authority List took 300.06882214546204s
Amount of data | Number of property check for Country Name Authority List took 0.1881415843963623s
Understandability | Number of label check for Country Name Authority List took 8.464669227600098s
Understandability | URI regex check for Country Name Authority List took 0.2547619342803955s
Understandability | Vocabs check for Country Name Authority List took 0.11333274841308594s
Verifiability | Authors check for Country Name Authority List took 0.2468101978302002s
Verifiability | Publishers check for Country Name Authority List took 0.21874332427978516s
Performance | Throughput check for Country Name Authority List took 10.859495639801025s
Amount of data | Check the number of entities for Country Name Authority List took 7.343292236328125e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.22313547134399414s
Interlinking | sameAs chians check for Country Name Authority List took 10.990174293518066s
Interlinking | skos check for Country Name Authority List took 0.41452598571777344s
Interlinking | skos check for Country Name Authority List took 0.24074029922485352s
Timeliness | dataset update frequency check for Country Name Authority List took 0.16722726821899414s
Currency | Creation date check for Country Name Authority List took 0.479586124420166s
Currency | Modification date check for Country Name Authority List took 0.2085869312286377s
Rep.Conc. | URIs length for Country Name Authority List took 472.6831889152527s
Interoperability | New vocabularies check for Country Name Authority List took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.19049358367919922s
Accuracy | Check Functional Property for Country Name Authority List took 0.18507981300354004s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.14844775199890137s
Accuracy | Check Empty annotation labels for Country Name Authority List took 34.33346104621887s
Accuracy | Check White space in annotation for Country Name Authority List took 3.0902228355407715s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6963183879852295s
Consistency | Disjoint class check for Country Name Authority List took 0.20657563209533691s
Consistency | Check Misplaced properties for Country Name Authority List took 300.45772099494934s
Consistency | Misplaced classes for Country Name Authority List took 8.39070463180542s
Consistency | Check Ontology hijacking for Country Name Authority List took 30.557770490646362s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 10.862810611724854s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.510586977005s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.052537679672241s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.561147928237915s
Security | Sign check for Country Name Authority List took 0.14782285690307617s
Availability | Check URIs Dereferenciability for Country Name Authority List took 4.129308700561523s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.8995513916015625s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.020977258682250977s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.430511474609375e-06s
Believability | Calculation of trust value for Country Name Authority List took 7.62939453125e-06s
INFO | --- Analysis for country-authority-list took 15416.204879283905s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.15487074851989746s
Availability | VoID file availability check for Courts thesaurus took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.28166913986206055s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.461143493652344e-05s
Believability | Calculation of trust value for Courts thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for courts-thesaurus took 3.094714641571045s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.445209741592407s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.00038814544677734375s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.7158246040344238s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.177757263183594e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for Covid-on-the-Web took 55.322710037231445s
Availability | SPARQL endpoint availability check for CPA 2008 took 26.3563334941864s
Availability | VoID file availability check for CPA 2008 took 0.0008232593536376953s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.7101700305938721s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.291534423828125e-05s
Believability | Calculation of trust value for CPA 2008 took 5.0067901611328125e-06s
INFO | --- Analysis for cpa-2008 took 128.52851104736328s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.35936689376831055s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005669593811035156s
Extra | Recovery of all triples for Cooperative Patent Classification took 50.310166120529175s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.1170921325683594s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.21220350265503s
Versatility | Languages check for Cooperative Patent Classification took 120.14224100112915s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.27689218521118s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.3140561580657959s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.3567211627960205s
Availability | RDF dump link check for Cooperative Patent Classification took 0.23088669776916504s
License | MR license check for Cooperative Patent Classification took 0.26215577125549316s
License | HR license check for Cooperative Patent Classification took 90.27950620651245s
Amount of data | Number of property check for Cooperative Patent Classification took 0.34467434883117676s
Understandability | Number of label check for Cooperative Patent Classification took 90.24234437942505s
Understandability | URI regex check for Cooperative Patent Classification took 0.7307615280151367s
Understandability | Vocabs check for Cooperative Patent Classification took 0.31061387062072754s
Verifiability | Authors check for Cooperative Patent Classification took 0.30746030807495117s
Verifiability | Publishers check for Cooperative Patent Classification took 0.24845051765441895s
Performance | Throughput check for Cooperative Patent Classification took 11.009078741073608s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.963180541992188e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.2277204990386963s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.22101688385009766s
Interlinking | skos check for Cooperative Patent Classification took 0.3149080276489258s
Interlinking | skos check for Cooperative Patent Classification took 0.2535114288330078s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.1905210018157959s
Currency | Creation date check for Cooperative Patent Classification took 0.6328158378601074s
Currency | Modification date check for Cooperative Patent Classification took 0.4896996021270752s
Rep.Conc. | URIs length for Cooperative Patent Classification took 209.26793217658997s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.25697755813598633s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 107.64141988754272s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9732091426849365s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.860669136047363s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.25319504737854004s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.49732756614685s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 64.84663486480713s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.6203398704528809s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.58203411102295s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.816845655441284s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.5347235202789307s
Security | Sign check for Cooperative Patent Classification took 0.3405649662017822s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.8648109436035156s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.1020259857177734s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.021294593811035156s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.9073486328125e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 8.106231689453125e-06s
INFO | --- Analysis for CPC took 1507.0326435565948s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.1699378490448s
Availability | VoID file availability check for CPC 2008 took 0.0008406639099121094s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.2852661609649658s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.6253204345703125e-05s
Believability | Calculation of trust value for CPC 2008 took 3.0040740966796875e-05s
INFO | --- Analysis for cpc-2008 took 127.34699082374573s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.459324598312378s
Availability | VoID file availability check for CPV  2003 took 0.0008640289306640625s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.39362454414367676s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020535707473754883s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.314018249511719e-05s
Believability | Calculation of trust value for CPV  2003 took 4.5299530029296875e-06s
INFO | --- Analysis for cpv-2003 took 116.77590847015381s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.459796667099s
Availability | VoID file availability check for CPV 2008 took 0.0007877349853515625s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.27971577644348145s
Reputation | Calculation of the PageRank for CPV 2008 took 0.023836374282836914s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0011172294616699219s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 7.295608520507812e-05s
Believability | Calculation of trust value for CPV 2008 took 5.7220458984375e-06s
INFO | --- Analysis for cpv-2008 took 128.34981608390808s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.73602509498596s
Availability | VoID file availability check for crowdsourcing-fb took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.6997010707855225s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 3.6716461181640625e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 6.67572021484375e-06s
INFO | --- Analysis for crowdsourcing-fb took 536.7196509838104s
Availability | SPARQL endpoint availability check for CRTM took 7.224082946777344e-05s
Availability | VoID file availability check for CRTM took 0.00033593177795410156s
Completeness | Calculation of interlinking completeness for CRTM took 0.2771141529083252s
Reputation | Calculation of the PageRank for CRTM took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for CRTM took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.1948089599609375e-05s
Believability | Calculation of trust value for CRTM took 8.344650268554688e-06s
INFO | --- Analysis for crtm took 6.108504056930542s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 3.910064697265625e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.7023231983184814s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 8.58306884765625e-06s
INFO | --- Analysis for crystal-eye took 3.899949789047241s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.707280397415161s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.38326120376586914s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 6.151199340820312e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 6.198883056640625e-06s
INFO | --- Analysis for ctic-public-dataset took 44.115134716033936s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 3.981590270996094e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.27736592292785645s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.02160811424255371s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0010328292846679688s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.6716461181640625e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.3909759521484375e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.013322353363037s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.7067537307739258s
Availability | VoID file availability check for CulturaLinkedData took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.27736926078796387s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020218849182128906s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 2.9325485229492188e-05s
Believability | Calculation of trust value for CulturaLinkedData took 7.867813110351562e-06s
INFO | --- Analysis for culturalinkeddata took 3.6210408210754395s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.25451040267944336s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.273972749710083s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0009455680847167969s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.172325134277344e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ares-or took 2.9568653106689453s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11542296409606934s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.27503466606140137s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.409385681152344e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.7220458984375e-06s
INFO | --- Analysis for cz-ares-rzp took 2.8599061965942383s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11594200134277344s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2770833969116211s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021035432815551758s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.504753112792969e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 5.245208740234375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.981834650039673s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.1241302490234375s
Availability | VoID file availability check for Integrated pollution registry took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2760937213897705s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020163536071777344s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.5762786865234375e-05s
Believability | Calculation of trust value for Integrated pollution registry took 4.76837158203125e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.935227870941162s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.12610650062561035s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2790238857269287s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007457733154296875s
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.0067901611328125e-06s
INFO | --- Analysis for cz-contracts took 2.8832294940948486s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 3.8623809814453125e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.27265501022338867s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.9325485229492188e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-courts took 2.9986376762390137s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.11516165733337402s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.270460844039917s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.170967102050781e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ctia-bans took 5.018740653991699s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.1151266098022461s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2754671573638916s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.337860107421875e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 5.245208740234375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.8328638076782227s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11588191986083984s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.2767333984375s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.361701965332031e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-focus took 2.845320463180542s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.11557483673095703s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2836949825286865s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.076957702636719e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.8480112552642822s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.11571002006530762s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2799839973449707s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.337860107421875e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.822381258010864s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 10.166451930999756s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0009455680847167969s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.27982115745544434s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02018284797668457s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 6.175041198730469e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 5.4836273193359375e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 22.96851658821106s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 10.079060554504395s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2760164737701416s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020322799682617188s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.147125244140625e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 4.0531158447265625e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 22.886232376098633s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 1.248356819152832s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2712705135345459s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02016425132751465s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.504753112792969e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-average-salaries took 4.243419170379639s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.4146542549133301s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.27723002433776855s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020139455795288086s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.4456422328948975s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.4690825939178467s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.27736926078796387s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020016193389892578s
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.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.743171691894531e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.489884376525879s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.418337345123291s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.27301716804504395s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020055294036865234s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.528594970703125e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.4334402084350586s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.416409969329834s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.28042149543762207s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020012378692626953s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.4809112548828125e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.423624038696289s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.41834259033203125s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.27398037910461426s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020009756088256836s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.409385681152344e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-regions took 3.145536422729492s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.4180457592010498s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2674887180328369s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020105600357055664s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.361701965332031e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.4164252281188965s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.41527247428894043s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2740817070007324s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.4809112548828125e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.4034135341644287s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.416095495223999s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2727949619293213s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.417741060256958s
Availability | SPARQL endpoint availability check for ATC groups took 0.1157233715057373s
Availability | VoID file availability check for ATC groups took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2893097400665283s
Reputation | Calculation of the PageRank for ATC groups took 0.0249481201171875s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.985664367675781e-05s
Believability | Calculation of trust value for ATC groups took 6.9141387939453125e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.8841300010681152s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.11606431007385254s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.27304720878601074s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.025725603103637695s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0016856193542480469s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.887580871582031e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.4836273193359375e-06s
INFO | --- Analysis for cz-fulfillments took 2.838912010192871s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.036933183670043945s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.2744605541229248s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020221710205078125s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.76837158203125e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ic took 3.2614426612854004s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.4055604934692383s
Availability | VoID file availability check for List of Czech data boxes took 0.0006613731384277344s
Extra | Recovery of all triples for List of Czech data boxes took 223.61592483520508s
Performance | Total latancy measurement for List of Czech data boxes took 0.6153569221496582s
Amount of data | Number of triples check for List of Czech data boxes took 84.66402459144592s
Interoperability | New terms check for List of Czech data boxes took 13.14975094795227s
Versatility | Languages check for List of Czech data boxes took 300.1767358779907s
Interpretability | Number of blank nodes check for List of Czech data boxes took 3.614537239074707s
Interpretability | RDF structures check for List of Czech data boxes took 0.5399823188781738s
Versatility | Serialization formats check for List of Czech data boxes took 1.2606186866760254s
Availability | RDF dump link check for List of Czech data boxes took 40.73970079421997s
License | MR license check for List of Czech data boxes took 0.5009925365447998s
License | HR license check for List of Czech data boxes took 300.13304352760315s
Amount of data | Number of property check for List of Czech data boxes took 0.37006640434265137s
Understandability | Number of label check for List of Czech data boxes took 5.644446849822998s
Understandability | URI regex check for List of Czech data boxes took 0.5731697082519531s
Understandability | Vocabs check for List of Czech data boxes took 0.2517406940460205s
Verifiability | Authors check for List of Czech data boxes took 0.3940122127532959s
Verifiability | Publishers check for List of Czech data boxes took 0.2135915756225586s
Performance | Throughput check for List of Czech data boxes took 10.905560970306396s
Amount of data | Check the number of entities for List of Czech data boxes took 3.0803966522216797s
Verifiability | Contribs. check for List of Czech data boxes took 1.902010440826416s
Interlinking | sameAs chians check for List of Czech data boxes took 2.81164288520813s
Interlinking | skos check for List of Czech data boxes took 0.4407463073730469s
Interlinking | skos check for List of Czech data boxes took 0.11847949028015137s
Timeliness | dataset update frequency check for List of Czech data boxes took 1.0589730739593506s
Currency | Creation date check for List of Czech data boxes took 4.265588760375977s
Currency | Modification date check for List of Czech data boxes took 0.8938803672790527s
Rep.Conc. | URIs length for List of Czech data boxes took 169.59736323356628s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.47759079933166504s
Accuracy | Check Functional Property for List of Czech data boxes took 0.1633434295654297s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.1549391746520996s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 81.14981889724731s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.0753817558288574s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.635878801345825s
Consistency | Disjoint class check for List of Czech data boxes took 0.20476794242858887s
Consistency | Check Misplaced properties for List of Czech data boxes took 80.09616351127625s
Consistency | Misplaced classes for List of Czech data boxes took 7.7605438232421875s
Consistency | Check Ontology hijacking for List of Czech data boxes took 74.67302632331848s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.401975393295288s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 63.65180420875549s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.6255366802215576s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.5275769233703613s
Security | Sign check for List of Czech data boxes took 0.20578384399414062s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 498.2076849937439s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 1.7047991752624512s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02095961570739746s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 4.1484832763671875e-05s
Believability | Calculation of trust value for List of Czech data boxes took 5.245208740234375e-06s
INFO | --- Analysis for cz-list-of-databoxes took 2435.601696252823s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12136173248291016s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.00034427642822265625s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 227.24851608276367s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6371817588806152s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 28.90111207962036s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.348273992538452s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1782886981964s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.525881052017212s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11792278289794922s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.5776288509368896s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 40.22081542015076s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14511418342590332s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.19516134262085s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.26697826385498047s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.641382932662964s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.29128336906433105s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15154767036437988s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.39628052711486816s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1853313446044922s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.66652798652649s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 75.08048629760742s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7511169910430908s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4513096809387207s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12179112434387207s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11724090576171875s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.23351335525512695s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8248510360717773s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2764427661895752s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 340.32624650001526s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.519157886505127s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11675357818603516s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11902046203613281s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 88.75094652175903s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.060689926147461s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 17.736068964004517s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13089489936828613s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 76.6659665107727s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.752564191818237s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 73.59358549118042s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.424574851989746s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 68.21074891090393s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.262150764465332s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.75372314453125s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1687147617340088s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 473.27842140197754s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6044390201568604s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1724071502685547s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0011603832244873047s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0728836059570312e-05s
INFO | --- Analysis for cz-nace took 2606.015077829361s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.30084753036499023s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005900859832763672s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 174.4925515651703s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8471040725708008s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.38070249557495117s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5991477966308594s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 57.635658502578735s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.46781420707702637s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17413544654846191s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.9787211418151855s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.29790401458740234s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3712191581726074s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.6246433258056641s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15729737281799316s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4908623695373535s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.38666510581970215s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16915559768676758s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.19101738929748535s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24157476425170898s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.899755954742432s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.843971252441406e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1506516933441162s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20449447631835938s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2954440116882324s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16189885139465332s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6694839000701904s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3580460548400879s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.31741809844970703s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 54.105660915374756s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15657281875610352s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1658036708831787s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15742087364196777s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 40.53535175323486s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.408200979232788s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.669663429260254s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18199396133422852s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.122180700302124s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.998097896575928s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 83.47936916351318s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.9484443664550781s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.3924977779388428s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.502802610397339s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20656871795654297s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4145963191986084s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 937.2388083934784s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5888371467590332s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0423274040222168s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.602836608886719e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.9073486328125e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.3909759521484375e-06s
INFO | --- Analysis for cz-nkod took 71598.29402399063s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.18638873100280762s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.2510225772857666s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.457069396972656e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.0067901611328125e-06s
INFO | --- Analysis for cz-orders took 3.930986166000366s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.17170143127441406s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005853176116943359s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 213.7091624736786s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.511704683303833s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 41.29130697250366s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 15.101051568984985s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1458239555359s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 3.2697041034698486s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.16664600372314453s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 1.295029640197754s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 38.45150589942932s
License | MR license check for Institutions of public power of the Czech Republic took 0.3300764560699463s
License | HR license check for Institutions of public power of the Czech Republic took 300.11568236351013s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.16416001319885254s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 3.6862258911132812s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.3407931327819824s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.15606260299682617s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.2145214080810547s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.18194198608398438s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.397346019744873s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.2010984420776367s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.6739282608032227s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 1.0208020210266113s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.1571502685546875s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.10260725021362305s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.23555970191955566s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.6369674205780029s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.19461941719055176s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 168.10044741630554s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.4631056785583496s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.10245895385742188s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.13664698600769043s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 91.17167782783508s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.100776195526123s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.616724729537964s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.10297656059265137s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 82.35814619064331s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.991157293319702s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 68.96600556373596s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.2880990505218506s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 71.56251406669617s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6315016746520996s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 1.0328071117401123s
Security | Sign check for Institutions of public power of the Czech Republic took 0.1324934959411621s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 447.3009934425354s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.9502899646759033s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021431922912597656s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.269050598144531e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ovm took 2260.0409274101257s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.09850072860717773s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.6766557693481445s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020869016647338867s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-ovm-agendas took 4.312342643737793s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 20.155524253845215s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007734298706054688s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.712155818939209s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.021035194396972656s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.605552673339844e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ruian took 114.04205107688904s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.3862638473510742s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.2447221279144287s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.081031799316406e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 3.9977269172668457s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.3750123977661133s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.2479383945465088s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.552436828613281e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.5186996459960938s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.35661745071411133s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.23752999305725098s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 2.7179718017578125e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.4167866706848145s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.09816527366638184s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.238128662109375s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.409385681152344e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 7.62939453125e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.0157089233398438s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.09764766693115234s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2511465549468994s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.4809112548828125e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.525367259979248s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.09700322151184082s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2485964298248291s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.5762786865234375e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.1205673217773438e-05s
INFO | --- Analysis for cz-sidc-drugs took 2.597428560256958s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.11149048805236816s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006103515625s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 207.90889930725098s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5246889591217041s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 23.347799062728882s
Interoperability | New terms check for Summary types of Czech institutions of public power took 14.05330228805542s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.0989558696747s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 8.090750932693481s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.10380387306213379s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 1.5978577136993408s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 37.47101616859436s
License | MR license check for Summary types of Czech institutions of public power took 0.10532164573669434s
License | HR license check for Summary types of Czech institutions of public power took 300.11506056785583s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.12813925743103027s
Understandability | Number of label check for Summary types of Czech institutions of public power took 9.50481653213501s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.22341609001159668s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.21032428741455078s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.2252049446105957s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.15180516242980957s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.445009469985962s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.1578445434570312s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 1.3705341815948486s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 1.338895320892334s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.14280009269714355s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.10308647155761719s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.23443937301635742s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.4700653553009033s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.25800561904907227s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 165.70720887184143s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.5583837032318115s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.10174322128295898s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.10021305084228516s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 83.47324728965759s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0504748821258545s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6308696269989014s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.12493085861206055s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 77.67525911331177s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.874269008636475s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 69.91396927833557s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.2931246757507324s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 70.39384865760803s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.629757881164551s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.8290970325469971s
Security | Sign check for Summary types of Czech institutions of public power took 0.15669679641723633s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 455.58389616012573s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.160475254058838s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02137017250061035s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.7206878662109375e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 6.198883056640625e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2270.6641550064087s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.09716486930847168s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.24106693267822266s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.7670135498046875e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.4227216243743896s
Availability | SPARQL endpoint availability check for State funding providers took 0.09839272499084473s
Availability | VoID file availability check for State funding providers took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for State funding providers took 0.24570798873901367s
Reputation | Calculation of the PageRank for State funding providers took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.9114227294921875e-05s
Believability | Calculation of trust value for State funding providers took 6.198883056640625e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.436784029006958s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.09767603874206543s
Availability | VoID file availability check for Organizations active in R&D took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.24683594703674316s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.076957702636719e-05s
Believability | Calculation of trust value for Organizations active in R&D took 7.152557373046875e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.147810697555542s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.09768295288085938s
Availability | VoID file availability check for R&D Programmes took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.7058219909667969s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.100799560546875e-05s
Believability | Calculation of trust value for R&D Programmes took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.439899444580078s
Availability | SPARQL endpoint availability check for R&D Projects took 0.09671449661254883s
Availability | VoID file availability check for R&D Projects took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.24600577354431152s
Reputation | Calculation of the PageRank for R&D Projects took 0.02016758918762207s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.124641418457031e-05s
Believability | Calculation of trust value for R&D Projects took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-projects took 2.5409512519836426s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.09715485572814941s
Availability | VoID file availability check for Institutional research plans took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.24667000770568848s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.220008850097656e-05s
Believability | Calculation of trust value for Institutional research plans took 6.198883056640625e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.5737287998199463s
Availability | SPARQL endpoint availability check for Results of R&D took 0.09544706344604492s
Availability | VoID file availability check for Results of R&D took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.2445378303527832s
Reputation | Calculation of the PageRank for Results of R&D took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.1961669921875e-05s
Believability | Calculation of trust value for Results of R&D took 6.4373016357421875e-06s
INFO | --- Analysis for cz-vavai-results took 2.536811590194702s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.0973818302154541s
Availability | VoID file availability check for Tenders in R&D took 0.0009984970092773438s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.24386262893676758s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.076957702636719e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.5409293174743652s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 5.7220458984375e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2497711181640625s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.361701965332031e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 7.62939453125e-06s
INFO | --- Analysis for czech_addresses took 4.039644241333008s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.584575891494751s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2495555877685547s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.02037835121154785s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for DanteLatinLoanwords took 3.8062920570373535s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3474001884460449s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0005688667297363281s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 127.75871467590332s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.9252212047576904s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 1.6221182346343994s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 3.931532621383667s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 106.01500701904297s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 10.187447786331177s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.8631834983825684s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.3983948230743408s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.9982342720031738s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 1.4689760208129883s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 75.19704222679138s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2527916431427002s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.9540326595306396s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.7311229705810547s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2185673713684082s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.2779252529144287s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2232053279876709s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.714196920394897s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 0.0001308917999267578s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2033836841583252s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 1.0351996421813965s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.5331790447235107s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.26824069023132324s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.22642993927001953s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.3709518909454346s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.1957716941833496s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 77.29848742485046s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.20084071159362793s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.42017555236816406s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.2720334529876709s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 38.36502718925476s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.129936933517456s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.607417583465576s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.24696898460388184s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 19.928981065750122s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.398329496383667s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 45.38979959487915s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4160304069519043s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 13.67627477645874s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.84368896484375s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.22100400924682617s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.32808995246887207s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 18.144182205200195s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 1.2457630634307861s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021393775939941406s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014710426330566406s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.9073486328125e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 8.58306884765625e-06s
INFO | --- Analysis for data-bnf-fr took 737.4285333156586s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.1345663070678711s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005679130554199219s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.6680963039398193s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.3554844856262207s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 5.395970821380615s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.151829957962036s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.08031678199768066s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.5796091556549072s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.038092851638793945s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.09810423851013184s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.09353327751159668s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.08001279830932617s
License | MR license check for Open Data from the Italian National Research Council took 0.09432673454284668s
License | HR license check for Open Data from the Italian National Research Council took 11.81633186340332s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.09581279754638672s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.8475706577301025s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.17146682739257812s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.08399128913879395s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.1539309024810791s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.08191990852355957s
Performance | Throughput check for Open Data from the Italian National Research Council took 10.31696343421936s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 3.075599670410156e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.08780765533447266s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.09011411666870117s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.08647918701171875s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.05835723876953125s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.0906684398651123s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.1764683723449707s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.17965221405029297s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 11.695655822753906s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.08045220375061035s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.0791928768157959s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.07945132255554199s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.4977376461029053s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.03291130065917969s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.027322053909301758s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.0814359188079834s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 9.961350440979004s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.18548107147216797s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.4873392581939697s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.2361812591552734s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 11.476606130599976s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03322458267211914s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.18899297714233398s
Security | Sign check for Open Data from the Italian National Research Council took 0.08413338661193848s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 560.1245012283325s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 1.2149715423583984s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.414817810058594e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.9604644775390625e-06s
INFO | --- Analysis for data-cnr-it took 660.5467844009399s
Availability | SPARQL endpoint availability check for Data.gov took 1.6221718788146973s
Availability | VoID file availability check for Data.gov took 0.0003600120544433594s
Completeness | Calculation of interlinking completeness for Data.gov took 0.25044965744018555s
Reputation | Calculation of the PageRank for Data.gov took 0.021095991134643555s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.2901763916015625e-05s
Believability | Calculation of trust value for Data.gov took 6.198883056640625e-06s
INFO | --- Analysis for data-gov took 18.287832021713257s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.16411638259887695s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.24990248680114746s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.104873657226562e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 6.67572021484375e-06s
INFO | --- Analysis for data-gov-ie took 3.2585320472717285s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.291534423828125e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.24711394309997559s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.152557373046875e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 6.4373016357421875e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.293313980102539s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 19.500123262405396s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0008082389831542969s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.24615716934204102s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.021321773529052734s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.842613220214844e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 8.58306884765625e-06s
INFO | --- Analysis for data-hnm-hu took 164.70402908325195s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.22179675102233887s
Availability | VoID file availability check for Climb Dataincubator took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2476978302001953s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.700920104980469e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-climb took 3.9036495685577393s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.267692565917969e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.24697327613830566s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.059906005859375e-05s
Believability | Calculation of trust value for Discogs in RDF took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-discogs took 6.424894094467163s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.052994728088378906s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0008001327514648438s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.24910616874694824s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.245208740234375e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-metoffice took 7.72292685508728s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.7840955257415771s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.2778642177581787s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.749961853027344e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-moseley took 8.854424715042114s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05059027671813965s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.24730944633483887s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020519256591796875s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.322166442871094e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.3209967613220215s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.648237705230713s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.25250792503356934s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007579326629638672s
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 5.9604644775390625e-06s
INFO | --- Analysis for data-incubator-nasa took 7.434062719345093s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.05259275436401367s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2418057918548584s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020307302474975586s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.700920104980469e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.3008933067321777s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.04924416542053223s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.248612642288208s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 8.96453857421875e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-pokedex took 3.953584909439087s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.05301523208618164s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.24660754203796387s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 0.00012087821960449219s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.305330753326416s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.6171174049377441s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006330013275146484s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 66.82482743263245s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.2175514698028564s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 0.257037878036499s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.4998853206634521s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 8.740068674087524s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 0.26215124130249023s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.1377735137939453s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.28256869316101074s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.3042113780975342s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.2552816867828369s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.2839992046356201s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 2.923229455947876s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.26009488105773926s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 0.43697428703308105s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.5160603523254395s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.27980613708496094s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.2859458923339844s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.2686607837677002s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.569239377975464s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 6.818771362304688e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.27379274368286133s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.2651548385620117s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.31278347969055176s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2764089107513428s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.27823495864868164s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.577359676361084s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.5486128330230713s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 51.1272337436676s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.2616100311279297s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2582426071166992s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2613554000854492s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 32.754512548446655s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.124943256378174s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.2593090534210205s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.7111237049102783s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 17.818424701690674s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.5478112697601318s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.00012993812561035156s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.4210379123687744s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.27155566215515137s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 1517.4812183380127s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 1.241377353668213s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.0267026424407959s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 9.059906005859375e-06s
INFO | --- Analysis for data-open-ac-uk took 1801.2819645404816s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.81927490234375s
Availability | VoID file availability check for Persée in RDF took 0.0006489753723144531s
Extra | Recovery of all triples for Persée in RDF took 1.536048412322998s
Performance | Total latancy measurement for Persée in RDF took 0.5743916034698486s
Amount of data | Number of triples check for Persée in RDF took 4.313369512557983s
Interoperability | New terms check for Persée in RDF took 1.7428526878356934s
Versatility | Languages check for Persée in RDF took 121.96763586997986s
Interpretability | Number of blank nodes check for Persée in RDF took 0.3917124271392822s
Interpretability | RDF structures check for Persée in RDF took 0.8618676662445068s
Versatility | Serialization formats check for Persée in RDF took 1.0693273544311523s
Availability | RDF dump link check for Persée in RDF took 0.3022785186767578s
License | MR license check for Persée in RDF took 1.650885820388794s
License | HR license check for Persée in RDF took 38.13005566596985s
Amount of data | Number of property check for Persée in RDF took 0.1237027645111084s
Understandability | Number of label check for Persée in RDF took 2.1811890602111816s
Understandability | URI regex check for Persée in RDF took 0.9437828063964844s
Understandability | Vocabs check for Persée in RDF took 0.4483010768890381s
Verifiability | Authors check for Persée in RDF took 0.1536107063293457s
Verifiability | Publishers check for Persée in RDF took 0.12303757667541504s
Performance | Throughput check for Persée in RDF took 10.543105363845825s
Amount of data | Check the number of entities for Persée in RDF took 3.9577484130859375e-05s
Verifiability | Contribs. check for Persée in RDF took 0.11730313301086426s
Interlinking | sameAs chians check for Persée in RDF took 0.1276836395263672s
Interlinking | skos check for Persée in RDF took 0.7864458560943604s
Interlinking | skos check for Persée in RDF took 0.1169891357421875s
Timeliness | dataset update frequency check for Persée in RDF took 0.7586486339569092s
Currency | Creation date check for Persée in RDF took 0.5468003749847412s
Currency | Modification date check for Persée in RDF took 0.2401268482208252s
Rep.Conc. | URIs length for Persée in RDF took 3.623265504837036s
Interoperability | New vocabularies check for Persée in RDF took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.11588501930236816s
Accuracy | Check Functional Property for Persée in RDF took 0.13146519660949707s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.13152289390563965s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.9445765018463135s
Accuracy | Check White space in annotation for Persée in RDF took 0.038990020751953125s
Accuracy | Check Datatype consistency for Persée in RDF took 0.02743053436279297s
Consistency | Disjoint class check for Persée in RDF took 0.5785732269287109s
Consistency | Check Misplaced properties for Persée in RDF took 2.6178343296051025s
Consistency | Misplaced classes for Persée in RDF took 0.20906639099121094s
Consistency | Check Ontology hijacking for Persée in RDF took 1.6947834491729736s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.1466610431671143s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.6222851276397705s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03267645835876465s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.11815834045410156s
Security | Sign check for Persée in RDF took 0.8307230472564697s
Availability | Check URIs Dereferenciability for Persée in RDF took 1163.6224582195282s
Completeness | Calculation of interlinking completeness for Persée in RDF took 1.300079107284546s
Reputation | Calculation of the PageRank for Persée in RDF took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011968612670898438s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.1920928955078125e-06s
Believability | Calculation of trust value for Persée in RDF took 7.62939453125e-06s
INFO | --- Analysis for data-persee-fr took 1409.6227428913116s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.076957702636719e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.6775534152984619s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.337860107421875e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 7.867813110351562e-06s
INFO | --- Analysis for data-southampton-ac-uk took 4.863257884979248s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.7255942821502686s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.00039458274841308594s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.23667502403259277s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.0001125335693359375s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 7.62939453125e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 8.423481464385986s
Availability | SPARQL endpoint availability check for Open Data Web took 0.12148094177246094s
Availability | VoID file availability check for Open Data Web took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.248976469039917s
Reputation | Calculation of the PageRank for Open Data Web took 0.020187854766845703s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Data Web took 8.344650268554688e-06s
INFO | --- Analysis for data.odw.tw took 2.344595193862915s
Availability | SPARQL endpoint availability check for DataFAQs took 4.00543212890625e-05s
Availability | VoID file availability check for DataFAQs took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.250347375869751s
Reputation | Calculation of the PageRank for DataFAQs took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.0040740966796875e-05s
Believability | Calculation of trust value for DataFAQs took 8.344650268554688e-06s
INFO | --- Analysis for datafaqs took 2.693206548690796s
Availability | SPARQL endpoint availability check for datahub took 4.1961669921875e-05s
Availability | VoID file availability check for datahub took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for datahub took 0.25190305709838867s
Reputation | Calculation of the PageRank for datahub took 0.020193099975585938s
Interlinking | Calculation of Degree of Connection for datahub took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for datahub took 4.744529724121094e-05s
Believability | Calculation of trust value for datahub took 9.059906005859375e-06s
INFO | --- Analysis for datahub took 2.7476649284362793s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 9.753644704818726s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.24947094917297363s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.02024364471435547s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.647804260253906e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 8.344650268554688e-06s
INFO | --- Analysis for datahub-kr-datamap took 20.108086347579956s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3412342071533203s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2511937618255615s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.128715515136719e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.152557373046875e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 4.618992328643799s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.171115398406982s
Availability | VoID file availability check for datos-artium-org took 0.0008027553558349609s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.7446551322937012s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011539459228515625s
Believability | Calculation of trust value for datos-artium-org took 6.67572021484375e-06s
INFO | --- Analysis for datos-artium-org took 165.78153777122498s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8617539405822754s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006113052368164062s
Extra | Recovery of all triples for Datos.bcn.cl took 57.934098958969116s
Performance | Total latancy measurement for Datos.bcn.cl took 5.935535192489624s
Amount of data | Number of triples check for Datos.bcn.cl took 3.9406285285949707s
Interoperability | New terms check for Datos.bcn.cl took 3.5275356769561768s
Versatility | Languages check for Datos.bcn.cl took 300.9915072917938s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.9675374031066895s
Security | Check HTTPS for Datos.bcn.cl took 0.7121374607086182s
Interpretability | RDF structures check for Datos.bcn.cl took 1.6564991474151611s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2824957370758057s
Availability | RDF dump link check for Datos.bcn.cl took 1.1852450370788574s
License | MR license check for Datos.bcn.cl took 1.2030224800109863s
License | HR license check for Datos.bcn.cl took 72.18528819084167s
Amount of data | Number of property check for Datos.bcn.cl took 1.4991402626037598s
Understandability | Number of label check for Datos.bcn.cl took 2.5167500972747803s
Understandability | URI regex check for Datos.bcn.cl took 2.3589324951171875s
Understandability | Vocabs check for Datos.bcn.cl took 1.1819634437561035s
Verifiability | Authors check for Datos.bcn.cl took 1.1930649280548096s
Verifiability | Publishers check for Datos.bcn.cl took 1.1836647987365723s
Performance | Throughput check for Datos.bcn.cl took 11.810682535171509s
Amount of data | Check the number of entities for Datos.bcn.cl took 5.888938903808594e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.1783642768859863s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.188307285308838s
Interlinking | skos check for Datos.bcn.cl took 1.206838846206665s
Interlinking | skos check for Datos.bcn.cl took 1.2163467407226562s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2138993740081787s
Currency | Creation date check for Datos.bcn.cl took 2.3876802921295166s
Currency | Modification date check for Datos.bcn.cl took 1.1902813911437988s
Rep.Conc. | URIs length for Datos.bcn.cl took 75.78442215919495s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.1772444248199463s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.1778042316436768s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.1818430423736572s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 24.96787452697754s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.24070167541503906s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.26413917541503906s
Consistency | Disjoint class check for Datos.bcn.cl took 1.1811892986297607s
Consistency | Check Misplaced properties for Datos.bcn.cl took 6.215731620788574s
Consistency | Misplaced classes for Datos.bcn.cl took 2.012263298034668s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 34.331815242767334s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.198843002319336s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 6.035504102706909s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.2929246425628662s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.395775318145752s
Security | Sign check for Datos.bcn.cl took 1.2107841968536377s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 8791.135298728943s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.5270557403564453s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02152872085571289s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 0.0001480579376220703s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 4.5299530029296875e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 7.867813110351562e-06s
INFO | --- Analysis for datos-bcn-cl took 9734.665489196777s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.3357205390930176s
Availability | VoID file availability check for datos.bne.es took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.2506895065307617s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011229515075683594s
Believability | Calculation of trust value for datos.bne.es took 6.198883056640625e-06s
INFO | --- Analysis for datos-bne-es took 4.949168682098389s
Availability | SPARQL endpoint availability check for dbacademic took 0.16324615478515625s
Availability | VoID file availability check for dbacademic took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for dbacademic took 0.23365354537963867s
Reputation | Calculation of the PageRank for dbacademic took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for dbacademic took 4.291534423828125e-05s
Believability | Calculation of trust value for dbacademic took 6.4373016357421875e-06s
INFO | --- Analysis for dbacademic took 3.304593563079834s
Availability | SPARQL endpoint availability check for DBkWik took 32.38923192024231s
Availability | VoID file availability check for DBkWik took 0.0003001689910888672s
Extra | Recovery of all triples for DBkWik took 11.31777572631836s
Amount of data | Number of triples check for DBkWik took 10.000353336334229s
Interoperability | New terms check for DBkWik took 17.96556520462036s
Versatility | Languages check for DBkWik took 10.042070388793945s
Interpretability | Number of blank nodes check for DBkWik took 121.13051342964172s
Interpretability | RDF structures check for DBkWik took 9.998361587524414s
Versatility | Serialization formats check for DBkWik took 10.000324964523315s
Availability | RDF dump link check for DBkWik took 9.99751353263855s
License | MR license check for DBkWik took 193.58498907089233s
License | HR license check for DBkWik took 10.018568992614746s
Amount of data | Number of property check for DBkWik took 127.93514609336853s
Understandability | Number of label check for DBkWik took 10.696776866912842s
Understandability | URI regex check for DBkWik took 39.15107989311218s
Understandability | Vocabs check for DBkWik took 3.1005988121032715s
Verifiability | Authors check for DBkWik took 16.7018461227417s
Verifiability | Publishers check for DBkWik took 11.829142332077026s
Amount of data | Check the number of entities for DBkWik took 8.678436279296875e-05s
Verifiability | Contribs. check for DBkWik took 49.99916076660156s
Interlinking | sameAs chians check for DBkWik took 9.999038696289062s
Interlinking | skos check for DBkWik took 28.2215313911438s
Interlinking | skos check for DBkWik took 11.472580671310425s
Timeliness | dataset update frequency check for DBkWik took 10.007189512252808s
Currency | Creation date check for DBkWik took 20.098828554153442s
Currency | Modification date check for DBkWik took 20.004453420639038s
Rep.Conc. | URIs length for DBkWik took 34.880979776382446s
Consistency | Deprecated classes/propertiers check for DBkWik took 9.869767665863037s
Accuracy | Check Empty annotation labels for DBkWik took 19.92891216278076s
Accuracy | Check White space in annotation for DBkWik took 0.023444652557373047s
Accuracy | Check Datatype consistency for DBkWik took 0.031046390533447266s
Consistency | Disjoint class check for DBkWik took 10.028690338134766s
Consistency | Check Ontology hijacking for DBkWik took 9.999777793884277s
Consistency | Check Invalid usage of undefined properties for DBkWik took 37.52953624725342s
Conciseness | Check Extensional conciseness for DBkWik took 0.032724618911743164s
Security | Sign check for DBkWik took 26.181684970855713s
Availability | Check URIs Dereferenciability for DBkWik took 22.179049253463745s
Completeness | Calculation of interlinking completeness for DBkWik took 0.7518007755279541s
Reputation | Calculation of the PageRank for DBkWik took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for DBkWik took 8.96453857421875e-05s
Believability | Calculation of trust value for DBkWik took 7.62939453125e-06s
INFO | --- Analysis for dbkwik took 11752.198195457458s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.100799560546875e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.677560567855835s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.0207669734954834s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011324882507324219s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 45.09382176399231s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.2907261848449707s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006017684936523438s
Extra | Recovery of all triples for dblp Knowledge Graph took 57.854007959365845s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.6914761066436768s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.12195706367492676s
Interoperability | New terms check for dblp Knowledge Graph took 1.7007033824920654s
Versatility | Languages check for dblp Knowledge Graph took 30.257303953170776s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.1851887702941895s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.14417099952697754s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.1428356170654297s
Availability | RDF dump link check for dblp Knowledge Graph took 0.1254291534423828s
License | MR license check for dblp Knowledge Graph took 0.15797829627990723s
License | HR license check for dblp Knowledge Graph took 30.126692056655884s
Amount of data | Number of property check for dblp Knowledge Graph took 0.1298832893371582s
Understandability | Number of label check for dblp Knowledge Graph took 0.5371763706207275s
Understandability | URI regex check for dblp Knowledge Graph took 0.26403045654296875s
Understandability | Vocabs check for dblp Knowledge Graph took 0.13974714279174805s
Verifiability | Authors check for dblp Knowledge Graph took 0.136613130569458s
Verifiability | Publishers check for dblp Knowledge Graph took 0.13901805877685547s
Performance | Throughput check for dblp Knowledge Graph took 11.034381866455078s
Amount of data | Check the number of entities for dblp Knowledge Graph took 3.528594970703125e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.14305710792541504s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.18038272857666016s
Interlinking | skos check for dblp Knowledge Graph took 0.1372666358947754s
Interlinking | skos check for dblp Knowledge Graph took 0.12871265411376953s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.14090466499328613s
Currency | Creation date check for dblp Knowledge Graph took 0.2717156410217285s
Currency | Modification date check for dblp Knowledge Graph took 0.27896785736083984s
Rep.Conc. | URIs length for dblp Knowledge Graph took 28.018396615982056s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.14157509803771973s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.12678050994873047s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.13170504570007324s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 17.520983695983887s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.05232310295105s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.002185583114624s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.1280200481414795s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.26442575454711914s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 18.545738458633423s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 18428.184817552567s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 4.170724391937256s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.7097554206848145s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.14700722694396973s
Security | Sign check for dblp Knowledge Graph took 0.1315922737121582s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 9.845728635787964s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 1.0675041675567627s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020987749099731445s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 6.723403930664062e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for dblp-kg took 18722.68782186508s
Availability | SPARQL endpoint availability check for dbnary took 0.24993538856506348s
Availability | VoID file availability check for dbnary took 0.0005431175231933594s
Extra | Recovery of all triples for dbnary took 1.6510260105133057s
Performance | Total latancy measurement for dbnary took 0.33315396308898926s
Amount of data | Number of triples check for dbnary took 1.3234474658966064s
Interoperability | New terms check for dbnary took 3.602564811706543s
Versatility | Languages check for dbnary took 61.308194637298584s
Interpretability | Number of blank nodes check for dbnary took 4.413832902908325s
Security | Check HTTPS for dbnary took 0.16035795211791992s
Interpretability | RDF structures check for dbnary took 0.10516953468322754s
Versatility | Serialization formats check for dbnary took 0.36341428756713867s
Availability | RDF dump link check for dbnary took 0.06839728355407715s
License | MR license check for dbnary took 0.11148619651794434s
License | HR license check for dbnary took 61.50766706466675s
Amount of data | Number of property check for dbnary took 0.09696102142333984s
Understandability | Number of label check for dbnary took 0.7148239612579346s
Understandability | URI regex check for dbnary took 0.13978099822998047s
Understandability | Vocabs check for dbnary took 0.310244083404541s
Verifiability | Authors check for dbnary took 0.11154985427856445s
Verifiability | Publishers check for dbnary took 0.06266069412231445s
Performance | Throughput check for dbnary took 10.352911472320557s
Amount of data | Check the number of entities for dbnary took 0.00010776519775390625s
Verifiability | Contribs. check for dbnary took 0.06452131271362305s
Interlinking | sameAs chians check for dbnary took 0.09501481056213379s
Interlinking | skos check for dbnary took 0.34377121925354004s
Interlinking | skos check for dbnary took 0.06528043746948242s
Timeliness | dataset update frequency check for dbnary took 0.15111112594604492s
Currency | Creation date check for dbnary took 0.18778300285339355s
Currency | Modification date check for dbnary took 0.1921861171722412s
Rep.Conc. | URIs length for dbnary took 11.623528718948364s
Interoperability | New vocabularies check for dbnary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.12828326225280762s
Accuracy | Check Functional Property for dbnary took 0.18594980239868164s
Accuracy | Check Inverse Functional Property for dbnary took 0.1180722713470459s
Accuracy | Check Empty annotation labels for dbnary took 0.6608996391296387s
Accuracy | Check White space in annotation for dbnary took 0.025037288665771484s
Accuracy | Check Datatype consistency for dbnary took 0.027395963668823242s
Consistency | Disjoint class check for dbnary took 0.0881953239440918s
Consistency | Check Misplaced properties for dbnary took 9.051551342010498s
Consistency | Misplaced classes for dbnary took 0.2536747455596924s
Consistency | Check Ontology hijacking for dbnary took 1.8303210735321045s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.2803044319152832s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.087965965270996s
Conciseness | Check Extensional conciseness for dbnary took 0.03198671340942383s
Conciseness | Check Intensional conciseness for dbnary took 0.16040277481079102s
Security | Sign check for dbnary took 0.08448600769042969s
Availability | Check URIs Dereferenciability for dbnary took 20.503999710083008s
Completeness | Calculation of interlinking completeness for dbnary took 0.6988615989685059s
Reputation | Calculation of the PageRank for dbnary took 0.02129077911376953s
Interlinking | Calculation of Degree of Connection for dbnary took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for dbnary took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.7697296142578125e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.1920928955078125e-06s
Believability | Calculation of trust value for dbnary took 8.106231689453125e-06s
INFO | --- Analysis for dbnary took 318.77405405044556s
Availability | SPARQL endpoint availability check for DBpedia took 0.4086451530456543s
Availability | VoID file availability check for DBpedia took 0.0003590583801269531s
Extra | Recovery of all triples for DBpedia took 4.2405359745025635s
Performance | Total latancy measurement for DBpedia took 0.962944746017456s
Amount of data | Number of triples check for DBpedia took 1.54649019241333s
Interoperability | New terms check for DBpedia took 5.836349248886108s
Versatility | Languages check for DBpedia took 31.854559898376465s
Interpretability | Number of blank nodes check for DBpedia took 0.19629955291748047s
Security | Check HTTPS for DBpedia took 0.11187386512756348s
Interpretability | RDF structures check for DBpedia took 0.6042208671569824s
Versatility | Serialization formats check for DBpedia took 0.27373647689819336s
Availability | RDF dump link check for DBpedia took 0.4955320358276367s
License | MR license check for DBpedia took 1.3103914260864258s
License | HR license check for DBpedia took 31.197682857513428s
Amount of data | Number of property check for DBpedia took 0.19910025596618652s
Understandability | Number of label check for DBpedia took 2.4613630771636963s
Understandability | URI regex check for DBpedia took 0.8968379497528076s
Understandability | Vocabs check for DBpedia took 0.5106406211853027s
Verifiability | Authors check for DBpedia took 0.41472744941711426s
Verifiability | Publishers check for DBpedia took 0.24722027778625488s
Performance | Throughput check for DBpedia took 11.289612531661987s
Amount of data | Check the number of entities for DBpedia took 6.985664367675781e-05s
Verifiability | Contribs. check for DBpedia took 0.31099653244018555s
Interlinking | sameAs chians check for DBpedia took 2.596552848815918s
Interlinking | skos check for DBpedia took 0.9178426265716553s
Interlinking | skos check for DBpedia took 0.18738722801208496s
Timeliness | dataset update frequency check for DBpedia took 0.19947481155395508s
Currency | Creation date check for DBpedia took 0.46440935134887695s
Currency | Modification date check for DBpedia took 0.4308593273162842s
Rep.Conc. | URIs length for DBpedia took 36.2171311378479s
Interoperability | New vocabularies check for DBpedia took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.2043614387512207s
Accuracy | Check Functional Property for DBpedia took 0.2035081386566162s
Accuracy | Check Inverse Functional Property for DBpedia took 0.29857373237609863s
Accuracy | Check Empty annotation labels for DBpedia took 2.822877883911133s
Accuracy | Check White space in annotation for DBpedia took 0.030696630477905273s
Accuracy | Check Datatype consistency for DBpedia took 0.027720928192138672s
Consistency | Disjoint class check for DBpedia took 0.3365790843963623s
Consistency | Check Misplaced properties for DBpedia took 31.036237716674805s
Consistency | Misplaced classes for DBpedia took 0.8326575756072998s
Consistency | Check Ontology hijacking for DBpedia took 1.9576754570007324s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.1836779117584229s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.526564121246338s
Conciseness | Check Extensional conciseness for DBpedia took 0.03153491020202637s
Conciseness | Check Intensional conciseness for DBpedia took 1.1387062072753906s
Security | Sign check for DBpedia took 0.2016618251800537s
Availability | Check URIs Dereferenciability for DBpedia took 6449.375787496567s
Completeness | Calculation of interlinking completeness for DBpedia took 1.5327470302581787s
Reputation | Calculation of the PageRank for DBpedia took 0.022407054901123047s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0008404254913330078s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.000993490219116211s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia took 6923.297817468643s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.26962971687316895s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.723403930664062e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 8.557955503463745s
Availability | SPARQL endpoint availability check for DBpedia Commons took 7.263382911682129s
Availability | VoID file availability check for DBpedia Commons took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.2580714225769043s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 8.559226989746094e-05s
Believability | Calculation of trust value for DBpedia Commons took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-commons took 18.87835192680359s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.00543212890625e-05s
Availability | VoID file availability check for DBpedia in German took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.25806212425231934s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.4849853515625e-05s
Believability | Calculation of trust value for DBpedia in German took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-de took 4.812408447265625s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.909067153930664s
Availability | VoID file availability check for DBpedia in Greek took 0.0007913112640380859s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.3442542552947998s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00020885467529296875s
Believability | Calculation of trust value for DBpedia in Greek took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-el took 46.816487312316895s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.900759220123291s
Availability | VoID file availability check for DBpedia in Spanish took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.6796014308929443s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 9.846687316894531e-05s
Believability | Calculation of trust value for DBpedia in Spanish took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-es took 6.820166110992432s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2607839107513428s
Availability | VoID file availability check for DBpedia in Basque took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.2653074264526367s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.0994415283203125e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-eu took 6.593261241912842s
Availability | SPARQL endpoint availability check for DBpedia in French took 136.38899564743042s
Availability | VoID file availability check for DBpedia in French took 0.0007078647613525391s
Extra | Recovery of all triples for DBpedia in French took 300.0647828578949s
Performance | Total latancy measurement for DBpedia in French took 101.56884813308716s
Amount of data | Number of triples check for DBpedia in French took 24.955581188201904s
Interoperability | New terms check for DBpedia in French took 25.843371629714966s
Versatility | Languages check for DBpedia in French took 10.057451009750366s
Interpretability | Number of blank nodes check for DBpedia in French took 20.508261680603027s
Interpretability | RDF structures check for DBpedia in French took 10.00074815750122s
Versatility | Serialization formats check for DBpedia in French took 10.002088785171509s
Availability | RDF dump link check for DBpedia in French took 9.99674105644226s
License | MR license check for DBpedia in French took 94.14373397827148s
License | HR license check for DBpedia in French took 300.03248143196106s
Amount of data | Number of property check for DBpedia in French took 21.802204370498657s
Understandability | Number of label check for DBpedia in French took 10.031785488128662s
Understandability | URI regex check for DBpedia in French took 52.301493644714355s
Understandability | Vocabs check for DBpedia in French took 10.08984088897705s
Verifiability | Authors check for DBpedia in French took 9.999252557754517s
Verifiability | Publishers check for DBpedia in French took 10.004030704498291s
Amount of data | Check the number of entities for DBpedia in French took 4.076957702636719e-05s
Verifiability | Contribs. check for DBpedia in French took 20.944833517074585s
Interlinking | sameAs chians check for DBpedia in French took 38.20269989967346s
Interlinking | skos check for DBpedia in French took 10.0370774269104s
Interlinking | skos check for DBpedia in French took 22.450218677520752s
Timeliness | dataset update frequency check for DBpedia in French took 20.999704837799072s
Currency | Creation date check for DBpedia in French took 44.52163577079773s
Currency | Modification date check for DBpedia in French took 39.71755361557007s
Rep.Conc. | URIs length for DBpedia in French took 327.6573164463043s
Interoperability | New vocabularies check for DBpedia in French took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 31.72336483001709s
Accuracy | Check Functional Property for DBpedia in French took 26.326954126358032s
Accuracy | Check Inverse Functional Property for DBpedia in French took 22.519410610198975s
Accuracy | Check Empty annotation labels for DBpedia in French took 253.6831090450287s
Accuracy | Check White space in annotation for DBpedia in French took 3.0439162254333496s
Consistency | Disjoint class check for DBpedia in French took 9.998696327209473s
Consistency | Check Ontology hijacking for DBpedia in French took 10.008716583251953s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 83.65619039535522s
Conciseness | Check Extensional conciseness for DBpedia in French took 0.00015282630920410156s
Security | Sign check for DBpedia in French took 22.75375199317932s
Completeness | Calculation of interlinking completeness for DBpedia in French took 1.370896816253662s
Reputation | Calculation of the PageRank for DBpedia in French took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 9.775161743164062e-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 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-fr took 3268.987540245056s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 30.258485317230225s
Availability | VoID file availability check for DBpedia in Japanese took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.2529740333557129s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010204315185546875s
Believability | Calculation of trust value for DBpedia in Japanese took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-ja took 125.06341290473938s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.100799560546875e-05s
Availability | VoID file availability check for dbpedia lite took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.6908266544342041s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.560585021972656e-05s
Believability | Calculation of trust value for dbpedia lite took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-lite took 24.576502084732056s
Availability | SPARQL endpoint availability check for DBpedia-Live took 3.981590270996094e-05s
Availability | VoID file availability check for DBpedia-Live took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.7099273204803467s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.552436828613281e-05s
Believability | Calculation of trust value for DBpedia-Live took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-live took 5.07127571105957s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.24945640563964844s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.7448015213012695s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02230691909790039s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0015537738800048828s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0003342628479003906s
Believability | Calculation of trust value for DBpedia in Dutch took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-nl took 3.5699284076690674s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 30.182411193847656s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0008146762847900391s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.26850008964538574s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.416175842285156e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-pt took 72.98082065582275s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.7018203735351562s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.02128148078918457s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.361701965332031e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-spotlight took 5.125460147857666s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.1484832763671875e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.26352953910827637s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.699562072753906e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.472437620162964s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.00543212890625e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.25981616973876953s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 2.765655517578125e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.2550690174102783s
Availability | SPARQL endpoint availability check for DBpedia took 7.343292236328125e-05s
Availability | VoID file availability check for DBpedia took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for DBpedia took 0.25224900245666504s
Reputation | Calculation of the PageRank for DBpedia took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for DBpedia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.9802322387695312e-05s
Believability | Calculation of trust value for DBpedia took 7.62939453125e-06s
INFO | --- Analysis for dbpedia_ took 2.790562868118286s
Availability | SPARQL endpoint availability check for DBTropes took 4.2438507080078125e-05s
Availability | VoID file availability check for DBTropes took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for DBTropes took 0.26404666900634766s
Reputation | Calculation of the PageRank for DBTropes took 0.020815610885620117s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.393692016601562e-05s
Believability | Calculation of trust value for DBTropes took 7.62939453125e-06s
INFO | --- Analysis for dbtropes took 3.0376460552215576s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.124641418457031e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.2612125873565674s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 2.0503997802734375e-05s
INFO | --- Analysis for dbtune took 2.8508830070495605s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.7206878662109375e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0003886222839355469s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2523648738861084s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.2928924560546875e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 5.6025590896606445s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.1961669921875e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.2616579532623291s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02018570899963379s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.361701965332031e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 6.026695728302002s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.938662528991699s
Availability | VoID file availability check for DBTune.org/classical took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.26137733459472656s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.081031799316406e-05s
Believability | Calculation of trust value for DBTune.org/classical took 8.821487426757812e-06s
INFO | --- Analysis for dbtune-classical took 22.467369318008423s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.354990005493164s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0003294944763183594s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2550537586212158s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.628036499023438e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 26.90699315071106s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.385145664215088s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2640378475189209s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.580352783203125e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 7.62939453125e-06s
INFO | --- Analysis for dbtune-magnatune took 23.92005681991577s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.371036529541016s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.26480770111083984s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010728836059570312s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.91810941696167s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.362980604171753s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.26436948776245117s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.3882598876953125e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-myspace took 17.907315731048584s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.172325134277344e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.25850582122802734s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.152557373046875e-06s
INFO | --- Analysis for dclg-openuplabs took 3.29404878616333s
Availability | SPARQL endpoint availability check for data.dcs took 4.9591064453125e-05s
Availability | VoID file availability check for data.dcs took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for data.dcs took 0.2592463493347168s
Reputation | Calculation of the PageRank for data.dcs took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for data.dcs took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for data.dcs took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.4849853515625e-05s
Believability | Calculation of trust value for data.dcs took 6.198883056640625e-06s
INFO | --- Analysis for dcs-sheffield took 2.5730907917022705s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 3.910064697265625e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.2608981132507324s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 2.8848648071289062e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 6.9141387939453125e-06s
INFO | --- Analysis for de-budget took 2.839245319366455s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.100799560546875e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2589259147644043s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.743171691894531e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.867813110351562e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 3.979187250137329s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.124641418457031e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.25064969062805176s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020770549774169922s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 5.1021575927734375e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 7.62939453125e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.600435256958008s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.1484832763671875e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.2580852508544922s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.123283386230469e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.867813110351562e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.8098230361938477s
Availability | SPARQL endpoint availability check for Demografie took 5.3882598876953125e-05s
Availability | VoID file availability check for Demografie took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Demografie took 0.2580223083496094s
Reputation | Calculation of the PageRank for Demografie took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.123283386230469e-05s
Believability | Calculation of trust value for Demografie took 7.62939453125e-06s
INFO | --- Analysis for demografie took 2.799994945526123s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.1961669921875e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.25450730323791504s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020952463150024414s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.647804260253906e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 7.867813110351562e-06s
INFO | --- Analysis for desaparecidos took 2.6801412105560303s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.124641418457031e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2669086456298828s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0006945133209228516s
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 9.5367431640625e-06s
INFO | --- Analysis for deustoentrepreneurship took 3.9421277046203613s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.124641418457031e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2635223865509033s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00011444091796875s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 7.62939453125e-06s
INFO | --- Analysis for deustotech took 3.9346930980682373s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.2135646343231201s
Availability | VoID file availability check for Deutsche Biographie took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2657618522644043s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.1961669921875e-05s
Believability | Calculation of trust value for Deutsche Biographie took 7.867813110351562e-06s
INFO | --- Analysis for deutsche-biographie took 3.923755168914795s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.57763671875e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2685573101043701s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.936622619628906e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.239776611328125e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.719216585159302s
Availability | SPARQL endpoint availability check for dev8d took 4.267692565917969e-05s
Availability | VoID file availability check for dev8d took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for dev8d took 0.2553682327270508s
Reputation | Calculation of the PageRank for dev8d took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for dev8d took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0009980201721191406s
Interlinking | Calculation of Clustering coefficient for dev8d took 8.225440979003906e-05s
Believability | Calculation of trust value for dev8d took 7.867813110351562e-06s
INFO | --- Analysis for dev8d took 2.6809322834014893s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.31462287902832s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007708072662353516s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.26444578170776367s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 6.031990051269531e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 8.106231689453125e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.82471466064453s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.1484832763671875e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.258345365524292s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 2.9087066650390625e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 7.3909759521484375e-06s
INFO | --- Analysis for DHSVM took 12.49537706375122s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 3.981590270996094e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.2624068260192871s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.3855438232421875e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 7.62939453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.853287696838379s
Availability | SPARQL endpoint availability check for Diavgeia took 5.078315734863281e-05s
Availability | VoID file availability check for Diavgeia took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.2582230567932129s
Reputation | Calculation of the PageRank for Diavgeia took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Diavgeia took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.058547973632812e-05s
Believability | Calculation of trust value for Diavgeia took 5.0067901611328125e-06s
INFO | --- Analysis for diavgeia took 5.261291742324829s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.220008850097656e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.2810814380645752s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0001246929168701172s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for didactalia took 8.118823051452637s
Availability | SPARQL endpoint availability check for diigo.feed took 4.076957702636719e-05s
Availability | VoID file availability check for diigo.feed took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.2599325180053711s
Reputation | Calculation of the PageRank for diigo.feed took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.8848648071289062e-05s
Believability | Calculation of trust value for diigo.feed took 7.867813110351562e-06s
INFO | --- Analysis for diigo-feed took 2.8316285610198975s
Availability | SPARQL endpoint availability check for DisGeNET took 2.8212080001831055s
Availability | VoID file availability check for DisGeNET took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2633354663848877s
Reputation | Calculation of the PageRank for DisGeNET took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00014734268188476562s
Believability | Calculation of trust value for DisGeNET took 9.298324584960938e-06s
INFO | --- Analysis for disgenet took 9.859704494476318s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.2577493190765381s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 9.298324584960938e-06s
INFO | --- Analysis for disk took 2.81058931350708s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.1484832763671875e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2597365379333496s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020660400390625s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.123283386230469e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 9.298324584960938e-06s
INFO | --- Analysis for distritos-zaragoza took 2.8521347045898438s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.1961669921875e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2597167491912842s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.1948089599609375e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 9.298324584960938e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 7.338292360305786s
Availability | SPARQL endpoint availability check for DM2E took 4.6253204345703125e-05s
Availability | VoID file availability check for DM2E took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for DM2E took 0.2863907814025879s
Reputation | Calculation of the PageRank for DM2E took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for DM2E took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DM2E took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010824203491210938s
Believability | Calculation of trust value for DM2E took 8.106231689453125e-06s
INFO | --- Analysis for dm2e took 3.3436408042907715s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 3.981590270996094e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.25994014739990234s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.147125244140625e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 8.58306884765625e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.8368475437164307s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.82546067237854s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.30939722061157227s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00014972686767578125s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 7.867813110351562e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 11.832281351089478s
Availability | SPARQL endpoint availability check for DOAP Store took 4.00543212890625e-05s
Availability | VoID file availability check for DOAP Store took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.25609421730041504s
Reputation | Calculation of the PageRank for DOAP Store took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for DOAP Store took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 2.7894973754882812e-05s
Believability | Calculation of trust value for DOAP Store took 6.9141387939453125e-06s
INFO | --- Analysis for doap_store took 2.8497812747955322s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.124641418457031e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.26109838485717773s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020870208740234375s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.67572021484375e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.4836273193359375e-06s
INFO | --- Analysis for doi took 7.604446649551392s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.076957702636719e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.26390910148620605s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.314018249511719e-05s
Believability | Calculation of trust value for Driggu Florentino took 6.67572021484375e-06s
INFO | --- Analysis for Driggu took 4.6959052085876465s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.864460229873657s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.266063928604126s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.361701965332031e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 7.3909759521484375e-06s
INFO | --- Analysis for drug-data-hifm took 41.532745361328125s
Availability | SPARQL endpoint availability check for dspace took 4.38690185546875e-05s
Availability | VoID file availability check for dspace took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for dspace took 0.258760929107666s
Reputation | Calculation of the PageRank for dspace took 0.020149707794189453s
Interlinking | Calculation of Degree of Connection for dspace took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for dspace took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for dspace took 2.956390380859375e-05s
Believability | Calculation of trust value for dspace took 7.3909759521484375e-06s
INFO | --- Analysis for dspace took 2.8362975120544434s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 3.9577484130859375e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.26114559173583984s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 2.765655517578125e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 7.62939453125e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.8713724613189697s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.40992522239685s
Availability | VoID file availability check for MetaLex Document Server took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.7550387382507324s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 5.340576171875e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.867813110351562e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 554.7491073608398s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.9284656047821045s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0009260177612304688s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.7012991905212402s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.6716461181640625e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.3909759521484375e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 15.470004081726074s
Availability | SPARQL endpoint availability check for DWS-Group took 4.267692565917969e-05s
Availability | VoID file availability check for DWS-Group took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2675318717956543s
Reputation | Calculation of the PageRank for DWS-Group took 0.02012324333190918s
Interlinking | Calculation of Degree of Connection for DWS-Group took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010371208190917969s
Believability | Calculation of trust value for DWS-Group took 7.62939453125e-06s
INFO | --- Analysis for dws-group took 3.37362003326416s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.744529724121094e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.7579526901245117s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020955801010131836s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.9325485229492188e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 7.3909759521484375e-06s
INFO | --- Analysis for E1 took 5.863341331481934s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.08273482322692871s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.26035618782043457s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02136087417602539s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011920928955078125s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-alaska took 2.8852500915527344s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.05747723579406738s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.264096736907959s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.364418029785156e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-cau took 2.9027764797210693s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.03316831588745117s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2610034942626953s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02034759521484375s
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.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.365776062011719e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.396064043045044s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.037627220153808594s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.713984489440918s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.965896606445312e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-cdrewu took 3.713369369506836s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.038631439208984375s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2687079906463623s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001361370086669922s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.4310553073883057s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.03156757354736328s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.00040459632873535156s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.262237548828125s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.025326251983642578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 9.083747863769531e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-famu took 2.3956282138824463s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.05247855186462402s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.25234460830688477s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012636184692382812s
Believability | Calculation of trust value for eagle-i @ Harvard University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-harvard took 2.4102582931518555s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.052922964096069336s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2541825771331787s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020266056060791016s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00011920928955078125s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.401825189590454s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.04492330551147461s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2564258575439453s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0010521411895751953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 8.416175842285156e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-howard took 2.6507699489593506s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.035424232482910156s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.26279687881469727s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.152557373046875e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.4098918437957764s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.03249549865722656s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.25675344467163086s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007154941558837891s
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 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-jsu took 2.417646646499634s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.03185248374938965s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.26003026962280273s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.9577484130859375e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-meharry took 2.398829698562622s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04122495651245117s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2613677978515625s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02211451530456543s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010323524475097656s
Believability | Calculation of trust value for eagle-i @ Montana State University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-montana took 2.4320950508117676s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.042288780212402344s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00033354759216308594s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.25757718086242676s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.369850158691406e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-msm took 2.4094951152801514s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.05119657516479492s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2622077465057373s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012612342834472656s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.4220800399780273s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.043607473373413086s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2557528018951416s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 7.176399230957031e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-psm took 2.4076294898986816s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.04341387748718262s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.26421427726745605s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 7.700920104980469e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-tsu took 2.4075803756713867s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.04210710525512695s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2584848403930664s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020123958587646484s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.246566772460938e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.4111781120300293s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.05450725555419922s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.25519442558288574s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010633468627929688s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.405768632888794s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.034108877182006836s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2573258876800537s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00011968612670898438s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 8.821487426757812e-06s
INFO | --- Analysis for eagle-i-upr took 2.4068472385406494s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.041356563568115234s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.25504636764526367s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020354747772216797s
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.000751495361328125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 5.9604644775390625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-utep took 2.3877222537994385s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.031325340270996094s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004074573516845703s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2579789161682129s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.653236389160156e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-utsa took 2.3830037117004395s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.24330949783325195s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.2655966281890869s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.322166442871094e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.625838041305542s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.0364077091217041s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2601890563964844s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020090818405151367s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.128715515136719e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-xula took 2.399775505065918s
Availability | SPARQL endpoint availability check for Emergency situation took 0.8118014335632324s
Availability | VoID file availability check for Emergency situation took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2618107795715332s
Reputation | Calculation of the PageRank for Emergency situation took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.6253204345703125e-05s
Believability | Calculation of trust value for Emergency situation took 8.344650268554688e-06s
INFO | --- Analysis for Earthquake took 3.714358329772949s
Availability | SPARQL endpoint availability check for ESO took 0.6162018775939941s
Availability | VoID file availability check for ESO took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for ESO took 0.25970458984375s
Reputation | Calculation of the PageRank for ESO took 0.020153284072875977s
Interlinking | Calculation of Degree of Connection for ESO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ESO took 7.82012939453125e-05s
Believability | Calculation of trust value for ESO took 7.152557373046875e-06s
INFO | --- Analysis for Earthquake_case took 4.587429046630859s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.3993399143218994s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2588684558868408s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020071983337402344s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010251998901367188s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for ecb-linked-data took 2.7460310459136963s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.398185729980469s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.2536942958831787s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.00543212890625e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.0067901611328125e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 10.335135698318481s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.7381796836853027s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0004076957702636719s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.26180577278137207s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020113706588745117s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.508827209472656e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 5.847909927368164s
Availability | SPARQL endpoint availability check for ECLAP took 21.336655616760254s
Availability | VoID file availability check for ECLAP took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for ECLAP took 0.265002965927124s
Reputation | Calculation of the PageRank for ECLAP took 0.020009517669677734s
Interlinking | Calculation of Degree of Connection for ECLAP took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ECLAP took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.552436828613281e-05s
Believability | Calculation of trust value for ECLAP took 6.9141387939453125e-06s
INFO | --- Analysis for eclap took 53.72755694389343s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.267692565917969e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.26253628730773926s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020392656326293945s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.1444091796875e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 7.3909759521484375e-06s
INFO | --- Analysis for ECNU-GISer took 3.9531333446502686s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.2438507080078125e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2586827278137207s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 6.508827209472656e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.62939453125e-06s
INFO | --- Analysis for ecs took 3.432831287384033s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.0531158447265625e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.2540924549102783s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.0279159545898438e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.8219001293182373s
Availability | SPARQL endpoint availability check for Edublogs took 4.100799560546875e-05s
Availability | VoID file availability check for Edublogs took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Edublogs took 0.4079124927520752s
Reputation | Calculation of the PageRank for Edublogs took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for Edublogs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Edublogs took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.584426879882812e-05s
Believability | Calculation of trust value for Edublogs took 6.9141387939453125e-06s
INFO | --- Analysis for edublogs took 4.015361309051514s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.3441145420074463s
Availability | VoID file availability check for education.data.gov.uk took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.292194128036499s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.96453857421875e-05s
Believability | Calculation of trust value for education.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for education-data-gov-uk took 4.192725658416748s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2588481903076172s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020119428634643555s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.152557373046875e-06s
INFO | --- Analysis for education-openuplabs took 2.8315329551696777s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.4791269302368s
Availability | VoID file availability check for Educational programs - SISVU took 0.0012674331665039062s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.7732799053192139s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.023758888244628906s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 6.389617919921875e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.867813110351562e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1322.7925214767456s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.742640495300293s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2541341781616211s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.021278858184814453s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0008561611175537109s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.124641418457031e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.9604644775390625e-06s
INFO | --- Analysis for eea took 8.232388973236084s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.47997593879699707s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.6931283473968506s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.316734313964844e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 6.67572021484375e-06s
INFO | --- Analysis for eea-rod took 6.866976737976074s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.17043113708496094s
Availability | VoID file availability check for EEA Vocabularies took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.25780248641967773s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020116567611694336s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 7.939338684082031e-05s
Believability | Calculation of trust value for EEA Vocabularies took 8.344650268554688e-06s
INFO | --- Analysis for eea-vocabularies took 5.884399652481079s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 3.9577484130859375e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.7009544372558594s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for ege-university-linked-open-data took 4.564013242721558s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.3892223834991455s
Availability | VoID file availability check for E-Government Ontology took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2623772621154785s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.02021646499633789s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 2.7418136596679688e-05s
Believability | Calculation of trust value for E-Government Ontology took 7.62939453125e-06s
INFO | --- Analysis for EGovOntology took 3.058675527572632s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5670909881591797s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007162094116210938s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.8228132724761963s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2321009635925293s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6858162879943848s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9033129215240479s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.33271765708923s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.7032740116119385s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5690474510192871s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8628971576690674s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24805331230163574s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.37383460998535156s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 5.888170480728149s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2523510456085205s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3136270046234131s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.49142003059387207s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2756965160369873s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2999756336212158s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27661609649658203s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.395822048187256s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 8.20159912109375e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28383517265319824s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24395155906677246s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3695797920227051s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.21299362182617188s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9290540218353271s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.289158821105957s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.49371814727783203s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.531749725341797s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.21938824653625488s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2939164638519287s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2600886821746826s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 0.921119213104248s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.027238130569458008s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02814960479736328s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2150251865386963s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.2387025356292725s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.45029687881469727s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.122877836227417s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1492269039154053s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.03639817237854s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03267860412597656s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4200594425201416s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.39118409156799316s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 2876.955418109894s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.533602237701416s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.984306335449219e-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 7.152557373046875e-06s
INFO | --- Analysis for ei2a took 19126.2396132946s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.363059997558594e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.7142717838287354s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010657310485839844s
Believability | Calculation of trust value for EIONET RDF Data took 5.7220458984375e-06s
INFO | --- Analysis for eionet-rdf took 5.5515875816345215s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.2438507080078125e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.25017356872558594s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 2.7894973754882812e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 7.3909759521484375e-06s
INFO | --- Analysis for ElgooG_ took 2.7888846397399902s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.076957702636719e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2592296600341797s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.7894973754882812e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.3909759521484375e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 3.271062135696411s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.213984251022339s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.26114511489868164s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.104873657226562e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 6.67572021484375e-06s
INFO | --- Analysis for elviajero took 18.816186666488647s
Availability | SPARQL endpoint availability check for EMN took 4.291534423828125e-05s
Availability | VoID file availability check for EMN took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for EMN took 0.25885891914367676s
Reputation | Calculation of the PageRank for EMN took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for EMN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EMN took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for EMN took 3.743171691894531e-05s
Believability | Calculation of trust value for EMN took 5.9604644775390625e-06s
INFO | --- Analysis for emn took 2.6197807788848877s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2584877014160156s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 4.9591064453125e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 6.198883056640625e-06s
INFO | --- Analysis for enakting-co2emission took 2.3715128898620605s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 7.271766662597656e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2633655071258545s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020198822021484375s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.6716461181640625e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for enakting-crime took 2.3519954681396484s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2564547061920166s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.600120544433594e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for enakting-energy took 2.3403849601745605s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.25666356086730957s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 8.678436279296875e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-mortality took 2.330113410949707s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.25830888748168945s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.552436828613281e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for enakting-nhs took 2.3457233905792236s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.25775885581970215s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.030632019042969e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 4.291534423828125e-06s
INFO | --- Analysis for enakting-population took 2.3415451049804688s
Availability | SPARQL endpoint availability check for Enel Shops took 4.172325134277344e-05s
Availability | VoID file availability check for Enel Shops took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2607269287109375s
Reputation | Calculation of the PageRank for Enel Shops took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 5.14984130859375e-05s
Believability | Calculation of trust value for Enel Shops took 8.344650268554688e-06s
INFO | --- Analysis for enel-shops took 2.822953224182129s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.458427429199219e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.2581675052642822s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0006880760192871094s
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 8.344650268554688e-06s
INFO | --- Analysis for energy-efficiency took 2.8136162757873535s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 5.435943603515625e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.25960302352905273s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.02054738998413086s
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.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.8236358165740967s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.506111145019531e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.26161670684814453s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.170967102050781e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.8273892402648926s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.26276063919067383s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020250320434570312s
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.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.846057653427124s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.25956273078918457s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.24249267578125e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.826962471008301s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 3.9577484130859375e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.2658669948577881s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020682334899902344s
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.0006992816925048828s
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 8.58306884765625e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.8919270038604736s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.25910210609436035s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.123283386230469e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.8239541053771973s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 3.910064697265625e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.2589089870452881s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.147125244140625e-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.857511043548584s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.769481897354126s
Availability | VoID file availability check for English Heritage Periods List took 0.0007658004760742188s
Extra | Recovery of all triples for English Heritage Periods List took 0.5248444080352783s
Performance | Total latancy measurement for English Heritage Periods List took 1.8611845970153809s
Amount of data | Number of triples check for English Heritage Periods List took 0.6158027648925781s
Versatility | Languages check for English Heritage Periods List took 0.33136844635009766s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.521803617477417s
Security | Check HTTPS for English Heritage Periods List took 0.24818897247314453s
Interpretability | RDF structures check for English Heritage Periods List took 0.3404872417449951s
Versatility | Serialization formats check for English Heritage Periods List took 0.5499882698059082s
Availability | RDF dump link check for English Heritage Periods List took 0.38832759857177734s
License | MR license check for English Heritage Periods List took 0.4536013603210449s
License | HR license check for English Heritage Periods List took 0.45963525772094727s
Amount of data | Number of property check for English Heritage Periods List took 0.5824604034423828s
Understandability | Number of label check for English Heritage Periods List took 0.7868447303771973s
Understandability | URI regex check for English Heritage Periods List took 0.8566851615905762s
Understandability | Vocabs check for English Heritage Periods List took 0.44233202934265137s
Verifiability | Authors check for English Heritage Periods List took 0.47797250747680664s
Verifiability | Publishers check for English Heritage Periods List took 0.512321949005127s
Performance | Throughput check for English Heritage Periods List took 12.221360683441162s
Amount of data | Check the number of entities for English Heritage Periods List took 8.392333984375e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.390805721282959s
Interlinking | sameAs chians check for English Heritage Periods List took 0.39679932594299316s
Interlinking | skos check for English Heritage Periods List took 0.4653759002685547s
Interlinking | skos check for English Heritage Periods List took 0.4219799041748047s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.5150749683380127s
Currency | Creation date check for English Heritage Periods List took 0.8357789516448975s
Currency | Modification date check for English Heritage Periods List took 0.910470724105835s
Rep.Conc. | URIs length for English Heritage Periods List took 0.7410440444946289s
Interoperability | New vocabularies check for English Heritage Periods List took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.3719513416290283s
Accuracy | Check Functional Property for English Heritage Periods List took 0.37571144104003906s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.38413047790527344s
Consistency | Disjoint class check for English Heritage Periods List took 0.36879563331604004s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3980441093444824s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.5704963207244873s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00014925003051757812s
Security | Sign check for English Heritage Periods List took 0.3813462257385254s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.26190924644470215s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020333528518676758s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.0994415283203125e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-periods-list took 59.940781593322754s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.34345412254333496s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.25570201873779297s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020191669464111328s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.218650817871094e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 5.245208740234375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 3.7159204483032227s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.2147834300994873s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.2566838264465332s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020124435424804688s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.409385681152344e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.245208740234375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 3.580810070037842s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 3.933906555175781e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.2614438533782959s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 2.6226043701171875e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 6.4373016357421875e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.8536925315856934s
Availability | SPARQL endpoint availability check for English WordNet took 4.100799560546875e-05s
Availability | VoID file availability check for English WordNet took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for English WordNet took 0.26386332511901855s
Reputation | Calculation of the PageRank for English WordNet took 0.020206928253173828s
Interlinking | Calculation of Degree of Connection for English WordNet took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for English WordNet took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.147125244140625e-05s
Believability | Calculation of trust value for English WordNet took 6.9141387939453125e-06s
INFO | --- Analysis for english-wordnet took 2.9790842533111572s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.076957702636719e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.25897979736328125s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 6.29425048828125e-05s
Believability | Calculation of trust value for English Heritage Places took 6.198883056640625e-06s
INFO | --- Analysis for englishheritage_places took 2.838131904602051s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.16388344764709473s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.25764942169189453s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020745515823364258s
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.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.869171142578125e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 8.58306884765625e-06s
INFO | --- Analysis for enipedia took 2.5154333114624023s
Availability | SPARQL endpoint availability check for Enslaved.org took 5.650520324707031e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2586054801940918s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02150416374206543s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.266334533691406e-05s
Believability | Calculation of trust value for Enslaved.org took 7.152557373046875e-06s
INFO | --- Analysis for enslaved.org took 6.41004204750061s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.053658485412597656s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00021457672119140625s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.25743699073791504s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 4.792213439941406e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 6.67572021484375e-06s
INFO | --- Analysis for entice-graph took 2.392961263656616s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.315376281738281e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.25695085525512695s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.457069396972656e-05s
Believability | Calculation of trust value for Entrez Gene took 7.152557373046875e-06s
INFO | --- Analysis for entrez_gene took 27.809802770614624s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.00543212890625e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.2505035400390625s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.02021026611328125s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 2.86102294921875e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene_extract took 2.7830209732055664s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0630507469177246s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.00034999847412109375s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.25152134895324707s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.02005767822265625s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.7206878662109375e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 6.198883056640625e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.219517707824707s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.31846094131469727s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2613351345062256s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0008356571197509766s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 5.364418029785156e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 6.4373016357421875e-06s
INFO | --- Analysis for environment-data-gov-uk took 10.225833892822266s
Availability | SPARQL endpoint availability check for EARTh took 270.37180495262146s
Availability | VoID file availability check for EARTh took 0.0008435249328613281s
Completeness | Calculation of interlinking completeness for EARTh took 0.29981493949890137s
Reputation | Calculation of the PageRank for EARTh took 0.02122211456298828s
Interlinking | Calculation of Degree of Connection for EARTh took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00011157989501953125s
Believability | Calculation of trust value for EARTh took 8.344650268554688e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 563.9119532108307s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.4629819393157959s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0002601146697998047s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 124.83520317077637s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.890934944152832s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 8.750426530838013s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 13.6644606590271s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.2163019180298s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.5165581703186035s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.2506399154663086s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 11.272569417953491s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.2692575454711914s
License | MR license check for Micka (EO metadata) @PSNC took 0.3720510005950928s
License | HR license check for Micka (EO metadata) @PSNC took 300.17892241477966s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.29709959030151367s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.6084723472595215s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.6949832439422607s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.41072893142700195s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.18355965614318848s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.24138617515563965s
Performance | Throughput check for Micka (EO metadata) @PSNC took 10.694405794143677s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 0.00011301040649414062s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.18128442764282227s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.1806812286376953s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4568135738372803s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.5476973056793213s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 7.024811744689941s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.46298646926879883s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.2136857509613037s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 170.64789080619812s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.17998242378234863s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.30436038970947266s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.22631621360778809s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 47.02043914794922s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.673931837081909s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.6450653076171875s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.17939543724060059s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 101.11722564697266s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.357725620269775s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 40.59278154373169s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.2698864936828613s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 84.66917562484741s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.7560815811157227s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5453360080718994s
Security | Sign check for Micka (EO metadata) @PSNC took 0.4674546718597412s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 17.620960235595703s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 1.3918347358703613s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 7.62939453125e-06s
INFO | --- Analysis for EO_metadata took 2305.6064307689667s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 5.793571472167969e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.7014424800872803s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02100062370300293s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 4.029273986816406e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 7.62939453125e-06s
INFO | --- Analysis for EOKP-Datasets took 5.533010482788086s
Availability | SPARQL endpoint availability check for EPA-CDR took 7.176399230957031e-05s
Availability | VoID file availability check for EPA-CDR took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.6939451694488525s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.647804260253906e-05s
Believability | Calculation of trust value for EPA-CDR took 6.9141387939453125e-06s
INFO | --- Analysis for epa-cdr took 8.04473328590393s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2578284740447998s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.390975952148438e-05s
Believability | Calculation of trust value for EPA-FRS took 6.4373016357421875e-06s
INFO | --- Analysis for epa-frs took 5.998127698898315s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.2438507080078125e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.26019287109375s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.552436828613281e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.245208740234375e-06s
INFO | --- Analysis for epa-rcra took 5.821058034896851s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.220008850097656e-05s
Availability | VoID file availability check for EPA-SRS took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.26015424728393555s
Reputation | Calculation of the PageRank for EPA-SRS took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.605552673339844e-05s
Believability | Calculation of trust value for EPA-SRS took 7.152557373046875e-06s
INFO | --- Analysis for epa-srs took 5.49822473526001s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.124641418457031e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2598433494567871s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.361701965332031e-05s
Believability | Calculation of trust value for EPA-TRI took 5.9604644775390625e-06s
INFO | --- Analysis for epa-tri took 5.535808324813843s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 3.933906555175781e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.2593975067138672s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020718812942504883s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.700920104980469e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 6.67572021484375e-06s
INFO | --- Analysis for epo took 2.840789794921875s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.027889728546142578s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.257749080657959s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001289844512939453s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.4205939769744873s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.47620320320129395s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.26110243797302246s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.487701416015625e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 7.867813110351562e-06s
INFO | --- Analysis for eprtr took 3.539736270904541s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.9017224311828613s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.2590036392211914s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.075599670410156e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 7.3909759521484375e-06s
INFO | --- Analysis for ERAKG took 3.686591386795044s
Availability | SPARQL endpoint availability check for reg took 4.291534423828125e-05s
Availability | VoID file availability check for reg took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for reg took 0.2565290927886963s
Reputation | Calculation of the PageRank for reg took 0.02050948143005371s
Interlinking | Calculation of Degree of Connection for reg took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for reg took 0.0008890628814697266s
Interlinking | Calculation of Clustering coefficient for reg took 1.2159347534179688e-05s
Believability | Calculation of trust value for reg took 7.867813110351562e-06s
INFO | --- Analysis for erg took 2.305549144744873s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.21326684951782227s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.25814175605773926s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.1948089599609375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.9604644775390625e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.738115072250366s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.4345855712890625e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0012810230255126953s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2611398696899414s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.96453857421875e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.9604644775390625e-06s
INFO | --- Analysis for esd-standards took 3.767409086227417s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.267692565917969e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.25621938705444336s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.2479248046875e-05s
Believability | Calculation of trust value for ESD-Toolkit took 6.4373016357421875e-06s
INFO | --- Analysis for esd-toolkit took 3.108968734741211s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.3392181396484375e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.2598128318786621s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.0517578125e-05s
Believability | Calculation of trust value for Dataset Esis took 8.106231689453125e-06s
INFO | --- Analysis for esislearning took 2.7399215698242188s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.267692565917969e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0013012886047363281s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2615084648132324s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.266334533691406e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 8.106231689453125e-06s
INFO | --- Analysis for ESV took 4.176392078399658s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.4912288188934326s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.26397204399108887s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 3.8303864002227783s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.254047393798828s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.26271581649780273s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020813941955566406s
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.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.605552673339844e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 8.106231689453125e-06s
INFO | --- Analysis for eu-agencies-bodies took 12.247485876083374s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 6.937980651855469e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.2511100769042969s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.170967102050781e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 8.106231689453125e-06s
INFO | --- Analysis for eu-dgt-tm took 2.792731523513794s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.3392181396484375e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2714822292327881s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.653236389160156e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 5.7220458984375e-06s
INFO | --- Analysis for eu-institutions took 5.6492109298706055s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.9172344207763672s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2639033794403076s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.552436828613281e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 6.198883056640625e-06s
INFO | --- Analysis for eu-parliament-media took 6.383469104766846s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.7779269218444824s
Availability | VoID file availability check for EU Who Is Who took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2627267837524414s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.838539123535156e-05s
Believability | Calculation of trust value for EU Who Is Who took 5.4836273193359375e-06s
INFO | --- Analysis for eu-who-is-who took 8.666398286819458s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.7898929119110107s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.25586891174316406s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.2438507080078125e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for eumida-linked-data took 7.12465238571167s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.27138376235961914s
Availability | VoID file availability check for European Nature Information System took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.2542572021484375s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00011610984802246094s
Believability | Calculation of trust value for European Nature Information System took 9.298324584960938e-06s
INFO | --- Analysis for eunis took 4.3603856563568115s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 4.458155155181885s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.25722265243530273s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.367134094238281e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for eur-lex-rdf took 11.954547882080078s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.6971855163574219s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.26224327087402344s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 3.147125244140625e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.3392181396484375e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 5.7220458984375e-06s
INFO | --- Analysis for eurobarometer-standard took 7.056605100631714s
Availability | SPARQL endpoint availability check for European Election Results took 0.8051989078521729s
Availability | VoID file availability check for European Election Results took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2603576183319092s
Reputation | Calculation of the PageRank for European Election Results took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.838539123535156e-05s
Believability | Calculation of trust value for European Election Results took 5.245208740234375e-06s
INFO | --- Analysis for european-election-results took 7.035611391067505s
Availability | SPARQL endpoint availability check for EPO patents took 1.1708288192749023s
Availability | VoID file availability check for EPO patents took 0.0006461143493652344s
Extra | Recovery of all triples for EPO patents took 37.47777009010315s
Performance | Total latancy measurement for EPO patents took 0.9113905429840088s
Amount of data | Number of triples check for EPO patents took 90.20103049278259s
Versatility | Languages check for EPO patents took 120.1777663230896s
Interpretability | Number of blank nodes check for EPO patents took 90.31574845314026s
Interpretability | RDF structures check for EPO patents took 0.19920086860656738s
Versatility | Serialization formats check for EPO patents took 0.21065926551818848s
Availability | RDF dump link check for EPO patents took 0.21374773979187012s
License | MR license check for EPO patents took 0.20844435691833496s
License | HR license check for EPO patents took 90.19226241111755s
Amount of data | Number of property check for EPO patents took 0.19326543807983398s
Understandability | Number of label check for EPO patents took 90.18182587623596s
Understandability | URI regex check for EPO patents took 0.4954795837402344s
Understandability | Vocabs check for EPO patents took 0.26327037811279297s
Verifiability | Authors check for EPO patents took 0.28849244117736816s
Verifiability | Publishers check for EPO patents took 0.21665287017822266s
Performance | Throughput check for EPO patents took 10.926725387573242s
Amount of data | Check the number of entities for EPO patents took 7.43865966796875e-05s
Verifiability | Contribs. check for EPO patents took 0.2373819351196289s
Interlinking | sameAs chians check for EPO patents took 0.20447397232055664s
Interlinking | skos check for EPO patents took 0.19471168518066406s
Interlinking | skos check for EPO patents took 0.2244424819946289s
Timeliness | dataset update frequency check for EPO patents took 0.31797242164611816s
Currency | Creation date check for EPO patents took 0.4603903293609619s
Currency | Modification date check for EPO patents took 0.3988802433013916s
Rep.Conc. | URIs length for EPO patents took 156.80017805099487s
Interoperability | New vocabularies check for EPO patents took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.19468450546264648s
Accuracy | Check Empty annotation labels for EPO patents took 17.891695737838745s
Accuracy | Check White space in annotation for EPO patents took 2.962824821472168s
Accuracy | Check Datatype consistency for EPO patents took 4.9472057819366455s
Consistency | Disjoint class check for EPO patents took 0.17766070365905762s
Consistency | Check Misplaced properties for EPO patents took 120.33447527885437s
Consistency | Check Ontology hijacking for EPO patents took 21.11287260055542s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.514538049697876s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.42459154129028s
Conciseness | Check Extensional conciseness for EPO patents took 2.81491756439209s
Conciseness | Check Intensional conciseness for EPO patents took 0.4096643924713135s
Security | Sign check for EPO patents took 0.29253721237182617s
Availability | Check URIs Dereferenciability for EPO patents took 1.6724176406860352s
Completeness | Calculation of interlinking completeness for EPO patents took 1.160144567489624s
Reputation | Calculation of the PageRank for EPO patents took 0.02270650863647461s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for EPO patents took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 2.1457672119140625e-06s
Believability | Calculation of trust value for EPO patents took 8.106231689453125e-06s
INFO | --- Analysis for European_Patent_Information took 1306.666389465332s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.076957702636719e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.25082993507385254s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for europeana-lod took 3.688964366912842s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 5.745887756347656e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0004000663757324219s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.7724637985229492s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.179115295410156e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 8.106231689453125e-06s
INFO | --- Analysis for europeana-lod-v1 took 8.447727680206299s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.050095558166503906s
Availability | VoID file availability check for Europeana SPARQL took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.255587100982666s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020304203033447266s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.553794860839844e-05s
Believability | Calculation of trust value for Europeana SPARQL took 6.67572021484375e-06s
INFO | --- Analysis for europeana-sparql took 4.180645704269409s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07708191871643066s
Availability | VoID file availability check for EuroSentiment took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.3081240653991699s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020529747009277344s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.62396240234375e-05s
Believability | Calculation of trust value for EuroSentiment took 7.62939453125e-06s
INFO | --- Analysis for eurosentiment took 3.1882596015930176s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.220008850097656e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.25963282585144043s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.963180541992188e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.4836273193359375e-06s
INFO | --- Analysis for eurostat-rdf took 12.292076349258423s
Availability | SPARQL endpoint availability check for EuroVoc took 5.934884786605835s
Availability | VoID file availability check for EuroVoc took 0.0006718635559082031s
Extra | Recovery of all triples for EuroVoc took 111.01694059371948s
Performance | Total latancy measurement for EuroVoc took 0.5835590362548828s
Amount of data | Number of triples check for EuroVoc took 103.85633730888367s
Interoperability | New terms check for EuroVoc took 118.92871141433716s
Versatility | Languages check for EuroVoc took 300.055869102478s
Interpretability | Number of blank nodes check for EuroVoc took 1.8267817497253418s
Security | Check HTTPS for EuroVoc took 0.32301783561706543s
Interpretability | RDF structures check for EuroVoc took 0.36992406845092773s
Versatility | Serialization formats check for EuroVoc took 2.662421703338623s
Availability | RDF dump link check for EuroVoc took 0.2991466522216797s
License | MR license check for EuroVoc took 0.1340949535369873s
License | HR license check for EuroVoc took 300.0752146244049s
Amount of data | Number of property check for EuroVoc took 0.16014862060546875s
Understandability | Number of label check for EuroVoc took 6.608935117721558s
Understandability | URI regex check for EuroVoc took 12.700279474258423s
Understandability | Vocabs check for EuroVoc took 0.1105189323425293s
Verifiability | Authors check for EuroVoc took 0.22024130821228027s
Verifiability | Publishers check for EuroVoc took 0.32312989234924316s
Performance | Throughput check for EuroVoc took 10.700263738632202s
Amount of data | Check the number of entities for EuroVoc took 6.771087646484375e-05s
Verifiability | Contribs. check for EuroVoc took 0.20662879943847656s
Interlinking | sameAs chians check for EuroVoc took 9.866409063339233s
Interlinking | skos check for EuroVoc took 0.5123846530914307s
Interlinking | skos check for EuroVoc took 0.42221856117248535s
Timeliness | dataset update frequency check for EuroVoc took 0.2494494915008545s
Currency | Creation date check for EuroVoc took 0.3321540355682373s
Currency | Modification date check for EuroVoc took 0.46880006790161133s
Rep.Conc. | URIs length for EuroVoc took 468.98553681373596s
Interoperability | New vocabularies check for EuroVoc took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.20632481575012207s
Accuracy | Check Functional Property for EuroVoc took 0.18845748901367188s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.17488551139831543s
Accuracy | Check Empty annotation labels for EuroVoc took 27.65705132484436s
Accuracy | Check White space in annotation for EuroVoc took 3.0610227584838867s
Accuracy | Check Datatype consistency for EuroVoc took 2.602893352508545s
Consistency | Disjoint class check for EuroVoc took 0.13275551795959473s
Consistency | Check Misplaced properties for EuroVoc took 300.4600031375885s
Consistency | Misplaced classes for EuroVoc took 8.388570308685303s
Consistency | Check Ontology hijacking for EuroVoc took 33.253318786621094s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.4245235919952393s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.2392854690552s
Conciseness | Check Extensional conciseness for EuroVoc took 3.0091731548309326s
Conciseness | Check Intensional conciseness for EuroVoc took 0.5688202381134033s
Security | Sign check for EuroVoc took 0.14220404624938965s
Availability | Check URIs Dereferenciability for EuroVoc took 3.92645263671875s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.0898528099060059s
Reputation | Calculation of the PageRank for EuroVoc took 0.021375417709350586s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 2.1457672119140625e-06s
Believability | Calculation of trust value for EuroVoc took 9.059906005859375e-06s
INFO | --- Analysis for eurovoc took 14346.11996102333s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 3.9577484130859375e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.7027513980865479s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.02102971076965332s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 3.814697265625e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 7.867813110351562e-06s
INFO | --- Analysis for eurovoc-in-skos took 5.02860689163208s
Availability | SPARQL endpoint availability check for European Television Heritage took 8.749961853027344e-05s
Availability | VoID file availability check for European Television Heritage took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.25548434257507324s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.9325485229492188e-05s
Believability | Calculation of trust value for European Television Heritage took 8.821487426757812e-06s
INFO | --- Analysis for euscreen took 2.8466756343841553s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.291534423828125e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2653512954711914s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.863739013671875e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 6.4373016357421875e-06s
INFO | --- Analysis for euskadi-farmacias took 5.445295572280884s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.9256579875946045s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.26790952682495117s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 4.601478576660156e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 7.3909759521484375e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 5.204933404922485s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.3363525867462158s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.25339508056640625s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 6.914138793945312e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 8.58306884765625e-06s
INFO | --- Analysis for eutc-productions took 6.809256553649902s
Availability | SPARQL endpoint availability check for EventMedia took 0.4142756462097168s
Availability | VoID file availability check for EventMedia took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2606992721557617s
Reputation | Calculation of the PageRank for EventMedia took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010848045349121094s
Believability | Calculation of trust value for EventMedia took 8.821487426757812e-06s
INFO | --- Analysis for event-media took 10.505676507949829s
Availability | SPARQL endpoint availability check for EventKG took 4.267692565917969e-05s
Availability | VoID file availability check for EventKG took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for EventKG took 0.25847578048706055s
Reputation | Calculation of the PageRank for EventKG took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.487701416015625e-05s
Believability | Calculation of trust value for EventKG took 8.106231689453125e-06s
INFO | --- Analysis for eventkg took 4.83837628364563s
Availability | SPARQL endpoint availability check for Eventseer took 0.8472802639007568s
Availability | VoID file availability check for Eventseer took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Eventseer took 0.25919532775878906s
Reputation | Calculation of the PageRank for Eventseer took 0.0201413631439209s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.76837158203125e-05s
Believability | Calculation of trust value for Eventseer took 7.62939453125e-06s
INFO | --- Analysis for eventseer took 3.213233709335327s
Availability | SPARQL endpoint availability check for Face Link took 7.891654968261719e-05s
Availability | VoID file availability check for Face Link took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Face Link took 0.2592489719390869s
Reputation | Calculation of the PageRank for Face Link took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Face Link took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.504753112792969e-05s
Believability | Calculation of trust value for Face Link took 8.106231689453125e-06s
INFO | --- Analysis for Face_Link took 2.354656457901001s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 3.981590270996094e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.25331544876098633s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 2.956390380859375e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 7.3909759521484375e-06s
INFO | --- Analysis for facebook-lids took 2.7761049270629883s
Availability | SPARQL endpoint availability check for Fact Forge took 4.076957702636719e-05s
Availability | VoID file availability check for Fact Forge took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.25701355934143066s
Reputation | Calculation of the PageRank for Fact Forge took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for Fact Forge took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 2.86102294921875e-05s
Believability | Calculation of trust value for Fact Forge took 8.106231689453125e-06s
INFO | --- Analysis for fact-forge took 2.8283636569976807s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5612938404083252s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.000286102294921875s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 109.40052151679993s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8872003555297852s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.17798137664795s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 12.997712135314941s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.154105424881s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.9992358684539795s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21224236488342285s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.126379489898682s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2196812629699707s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.35420775413513184s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.17920207977295s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.38462162017822266s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.513293743133545s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6797943115234375s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.32656002044677734s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18102526664733887s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.24381113052368164s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.580241203308105s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.200241088867188e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1777341365814209s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1764209270477295s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.45632314682006836s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.45442819595336914s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.861952066421509s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4609105587005615s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21425771713256836s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 154.09874629974365s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17992949485778809s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.27266645431518555s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2774176597595215s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 39.191455125808716s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6495907306671143s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6782143115997314s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17577695846557617s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 85.2398316860199s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.312455177307129s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 37.927083015441895s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2882411479949951s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 96.55378890037537s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.738119125366211s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5562140941619873s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4273412227630615s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.043988227844238s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.901625394821167s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.02137923240661621s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.00010728836059570312s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for FADN_(2019) took 2278.4251091480255s
Availability | SPARQL endpoint availability check for FAMEData took 4.291534423828125e-05s
Availability | VoID file availability check for FAMEData took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for FAMEData took 0.3024864196777344s
Reputation | Calculation of the PageRank for FAMEData took 0.02319788932800293s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0015048980712890625s
Interlinking | Calculation of Clustering coefficient for FAMEData took 6.103515625e-05s
Believability | Calculation of trust value for FAMEData took 8.106231689453125e-06s
INFO | --- Analysis for famedata took 65.30192375183105s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.27497124671936035s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.417533874511719e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 5.245208740234375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.910868167877197s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.285611629486084s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00036144256591796875s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.29970645904541016s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010132789611816406s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for fao-linked-data took 5.248135328292847s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.076957702636719e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.2816627025604248s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.528594970703125e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for FAO_species took 3.797791004180908s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.55826473236084s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2900867462158203s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.315376281738281e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 8.106231689453125e-06s
INFO | --- Analysis for farmbio-chembl took 65.53694534301758s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 3.910064697265625e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.27211689949035645s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 7.62939453125e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 3.540557622909546s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.00543212890625e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.718602180480957s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for farolapp-dataset took 4.313775062561035s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 3.933906555175781e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.2617199420928955s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 2.86102294921875e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 7.867813110351562e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 3.4895174503326416s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.100799560546875e-05s
Availability | VoID file availability check for I4.0-Onto took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.25263452529907227s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020132064819335938s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.765655517578125e-05s
Believability | Calculation of trust value for I4.0-Onto took 8.58306884765625e-06s
INFO | --- Analysis for fatimazahra took 2.4467084407806396s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 3.838539123535156e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.26717042922973633s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.337860107421875e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 8.344650268554688e-06s
INFO | --- Analysis for federal-economic-rdf took 3.0628204345703125s
Availability | SPARQL endpoint availability check for Feed Wrapper took 3.981590270996094e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.28097033500671387s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 2.8371810913085938e-05s
Believability | Calculation of trust value for Feed Wrapper took 7.152557373046875e-06s
INFO | --- Analysis for feedwrapper-lids took 3.042078971862793s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.0531158447265625e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2841506004333496s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.8848648071289062e-05s
Believability | Calculation of trust value for FHIR STU3 took 6.9141387939453125e-06s
INFO | --- Analysis for FHIR_STU3 took 2.8900985717773438s
Availability | SPARQL endpoint availability check for FiESTA took 4.124641418457031e-05s
Availability | VoID file availability check for FiESTA took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for FiESTA took 0.26534509658813477s
Reputation | Calculation of the PageRank for FiESTA took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.62396240234375e-05s
Believability | Calculation of trust value for FiESTA took 9.059906005859375e-06s
INFO | --- Analysis for fiesta took 12.727872133255005s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.863739013671875e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.29914236068725586s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.075599670410156e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 6.9141387939453125e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.505007266998291s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 8.678436279296875e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2977328300476074s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.02033829689025879s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.651878356933594e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.7220458984375e-06s
INFO | --- Analysis for finnish-municipalities took 3.7282700538635254s
Availability | SPARQL endpoint availability check for firmao took 3.886222839355469e-05s
Availability | VoID file availability check for firmao took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for firmao took 0.2774078845977783s
Reputation | Calculation of the PageRank for firmao took 0.021183013916015625s
Interlinking | Calculation of Degree of Connection for firmao took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for firmao took 3.24249267578125e-05s
Believability | Calculation of trust value for firmao took 9.298324584960938e-06s
INFO | --- Analysis for firmao took 3.0771267414093018s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 5.364418029785156e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.2613182067871094s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 2.9802322387695312e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.9826736450195312s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.20723271369934082s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.00023221969604492188s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 113.0286033153534s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 1.0087032318115234s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 8.647490501403809s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.481001377105713s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.2233853340149s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.7395975589752197s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.2394709587097168s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 10.720458269119263s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.3150479793548584s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.5806028842926025s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.1363298892975s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.2128467559814453s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.36069655418396s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.6235194206237793s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.33553290367126465s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.20113468170166016s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.2542266845703125s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.065942525863647s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 6.723403930664062e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.2114100456237793s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.21434950828552246s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4426307678222656s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4638845920562744s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 7.8298680782318115s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.5170590877532959s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.24602723121643066s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 169.94167470932007s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.20394635200500488s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.178497314453125s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.32956552505493164s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 42.901657819747925s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6465182304382324s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.6519999504089355s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.21281838417053223s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 93.90170741081238s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.571074724197388s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 36.9283652305603s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.2598869800567627s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 92.8790397644043s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.737978219985962s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5521359443664551s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.7133679389953613s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 5.026360750198364s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 1.595736026763916s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.021022558212280273s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 2303.2101645469666s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.1961669921875e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.7290630340576172s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.368492126464844e-05s
Believability | Calculation of trust value for Fishes of Texas took 7.152557373046875e-06s
INFO | --- Analysis for fishes-of-texas took 4.736762762069702s
Availability | SPARQL endpoint availability check for flickr? wrappr took 5.14984130859375e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.2773561477661133s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.775161743164062e-05s
Believability | Calculation of trust value for flickr? wrappr took 7.62939453125e-06s
INFO | --- Analysis for flickr-wrappr took 4.792778491973877s
Availability | SPARQL endpoint availability check for flickr.person took 4.00543212890625e-05s
Availability | VoID file availability check for flickr.person took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for flickr.person took 0.2695798873901367s
Reputation | Calculation of the PageRank for flickr.person took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for flickr.person took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for flickr.person took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for flickr.person took 2.8848648071289062e-05s
Believability | Calculation of trust value for flickr.person took 6.9141387939453125e-06s
INFO | --- Analysis for flickr_person took 3.982897996902466s
Availability | SPARQL endpoint availability check for flickr.videoobject took 3.910064697265625e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.2691786289215088s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020833969116210938s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 2.8848648071289062e-05s
Believability | Calculation of trust value for flickr.videoobject took 6.9141387939453125e-06s
INFO | --- Analysis for flickr_videoobject took 3.061875104904175s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.00543212890625e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0007894039154052734s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.28718137741088867s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Future land use simulation model took 8.344650268554688e-06s
INFO | --- Analysis for FLUS took 9.061082601547241s
Availability | SPARQL endpoint availability check for Fly-TED took 4.029273986816406e-05s
Availability | VoID file availability check for Fly-TED took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.2931203842163086s
Reputation | Calculation of the PageRank for Fly-TED took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.266334533691406e-05s
Believability | Calculation of trust value for Fly-TED took 8.106231689453125e-06s
INFO | --- Analysis for fly-ted took 2.9928271770477295s
Availability | SPARQL endpoint availability check for FlyAtlas took 3.981590270996094e-05s
Availability | VoID file availability check for FlyAtlas took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.28446173667907715s
Reputation | Calculation of the PageRank for FlyAtlas took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.075599670410156e-05s
Believability | Calculation of trust value for FlyAtlas took 8.344650268554688e-06s
INFO | --- Analysis for flyatlas took 3.1090316772460938s
Availability | SPARQL endpoint availability check for Flybase took 1.7480316162109375s
Availability | VoID file availability check for Flybase took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for Flybase took 0.2783946990966797s
Reputation | Calculation of the PageRank for Flybase took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Flybase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.600120544433594e-05s
Believability | Calculation of trust value for Flybase took 7.62939453125e-06s
INFO | --- Analysis for flybase took 10.3367178440094s
Availability | SPARQL endpoint availability check for Flyted took 1.4416234493255615s
Availability | VoID file availability check for Flyted took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Flyted took 0.323744535446167s
Reputation | Calculation of the PageRank for Flyted took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for Flyted took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0994415283203125e-05s
Believability | Calculation of trust value for Flyted took 7.62939453125e-06s
INFO | --- Analysis for flyted took 11.55584979057312s
Availability | SPARQL endpoint availability check for Foodista took 1.0984911918640137s
Availability | VoID file availability check for Foodista took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Foodista took 0.30249881744384766s
Reputation | Calculation of the PageRank for Foodista took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.1948089599609375e-05s
Believability | Calculation of trust value for Foodista took 8.821487426757812e-06s
INFO | --- Analysis for foodista took 10.300756931304932s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.3776364326477051s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2879359722137451s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.390975952148438e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 8.106231689453125e-06s
INFO | --- Analysis for foodpedia took 3.025294303894043s
Availability | SPARQL endpoint availability check for FORGE Course information took 7.843971252441406e-05s
Availability | VoID file availability check for FORGE Course information took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.3008549213409424s
Reputation | Calculation of the PageRank for FORGE Course information took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.170967102050781e-05s
Believability | Calculation of trust value for FORGE Course information took 7.867813110351562e-06s
INFO | --- Analysis for forge-course-information took 3.109922170639038s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.172325134277344e-05s
Availability | VoID file availability check for FrameBase schema took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.2990233898162842s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02094864845275879s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0009424686431884766s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 5.435943603515625e-05s
Believability | Calculation of trust value for FrameBase schema took 8.106231689453125e-06s
INFO | --- Analysis for framebase-schema took 3.124891996383667s
Availability | SPARQL endpoint availability check for FrameNet took 3.9577484130859375e-05s
Availability | VoID file availability check for FrameNet took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for FrameNet took 0.2775864601135254s
Reputation | Calculation of the PageRank for FrameNet took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.1948089599609375e-05s
Believability | Calculation of trust value for FrameNet took 8.106231689453125e-06s
INFO | --- Analysis for framenet took 3.0652666091918945s
Availability | SPARQL endpoint availability check for Framester took 5.1975250244140625e-05s
Availability | VoID file availability check for Framester took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Framester took 0.2736477851867676s
Reputation | Calculation of the PageRank for Framester took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Framester took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Framester took 7.343292236328125e-05s
Believability | Calculation of trust value for Framester took 8.344650268554688e-06s
INFO | --- Analysis for framester took 3.5224697589874268s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.1608574390411377s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2987544536590576s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.58306884765625e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for frb-linked-data took 2.7530760765075684s
Availability | SPARQL endpoint availability check for Freebase took 4.124641418457031e-05s
Availability | VoID file availability check for Freebase took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Freebase took 0.2809271812438965s
Reputation | Calculation of the PageRank for Freebase took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0002651214599609375s
Believability | Calculation of trust value for Freebase took 6.9141387939453125e-06s
INFO | --- Analysis for freebase took 4.131489038467407s
Availability | SPARQL endpoint availability check for Freeyork took 4.172325134277344e-05s
Availability | VoID file availability check for Freeyork took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2864372730255127s
Reputation | Calculation of the PageRank for Freeyork took 0.02090764045715332s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010728836059570312s
Believability | Calculation of trust value for Freeyork took 6.9141387939453125e-06s
INFO | --- Analysis for freeyork-org took 3.134690046310425s
Availability | SPARQL endpoint availability check for French School Program took 4.029273986816406e-05s
Availability | VoID file availability check for French School Program took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for French School Program took 0.2622032165527344s
Reputation | Calculation of the PageRank for French School Program took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for French School Program took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.123283386230469e-05s
Believability | Calculation of trust value for French School Program took 7.867813110351562e-06s
INFO | --- Analysis for french-school-program took 2.9801430702209473s
Availability | SPARQL endpoint availability check for French School System took 3.981590270996094e-05s
Availability | VoID file availability check for French School System took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for French School System took 0.28577756881713867s
Reputation | Calculation of the PageRank for French School System took 0.020862102508544922s
Interlinking | Calculation of Degree of Connection for French School System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for French School System took 3.3855438232421875e-05s
Believability | Calculation of trust value for French School System took 8.106231689453125e-06s
INFO | --- Analysis for french-school-system took 3.0981228351593018s
Availability | SPARQL endpoint availability check for French TimeBank took 4.00543212890625e-05s
Availability | VoID file availability check for French TimeBank took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.2818126678466797s
Reputation | Calculation of the PageRank for French TimeBank took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.123283386230469e-05s
Believability | Calculation of trust value for French TimeBank took 7.867813110351562e-06s
INFO | --- Analysis for french-timebank took 3.1096231937408447s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.6849052906036377s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.2711668014526367s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.43865966796875e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.44824481010437s
Availability | SPARQL endpoint availability check for DailyMed took 0.6573173999786377s
Availability | VoID file availability check for DailyMed took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2789645195007324s
Reputation | Calculation of the PageRank for DailyMed took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.799003601074219e-05s
Believability | Calculation of trust value for DailyMed took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.509120941162109s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.6980805397033691s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2679901123046875s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 9.179115295410156e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.389885902404785s
Availability | SPARQL endpoint availability check for Diseasome took 0.6862666606903076s
Availability | VoID file availability check for Diseasome took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2924797534942627s
Reputation | Calculation of the PageRank for Diseasome took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for Diseasome took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diseasome took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011086463928222656s
Believability | Calculation of trust value for Diseasome took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.537985563278198s
Availability | SPARQL endpoint availability check for DrugBank took 0.6936700344085693s
Availability | VoID file availability check for DrugBank took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for DrugBank took 0.29950451850891113s
Reputation | Calculation of the PageRank for DrugBank took 0.020328998565673828s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011491775512695312s
Believability | Calculation of trust value for DrugBank took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.529983997344971s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.671360969543457s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.28730058670043945s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.361701965332031e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.563229560852051s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6753408908843994s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.28099846839904785s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.390975952148438e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.4086174964904785s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6723520755767822s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2572147846221924s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020582199096679688s
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.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.510185241699219e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-eures took 4.373718738555908s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6698489189147949s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.00039386749267578125s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2759873867034912s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.465217590332031e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 3.1948089599609375e-05s
INFO | --- Analysis for fu-berlin-eurostat took 4.983731985092163s
Availability | SPARQL endpoint availability check for MediCare took 0.7330496311187744s
Availability | VoID file availability check for MediCare took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for MediCare took 0.482724666595459s
Reputation | Calculation of the PageRank for MediCare took 0.020134687423706055s
Interlinking | Calculation of Degree of Connection for MediCare took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for MediCare took 3.719329833984375e-05s
Believability | Calculation of trust value for MediCare took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-medicare took 5.291205644607544s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7161972522735596s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.28341031074523926s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.343292236328125e-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.47694730758667s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6793396472930908s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.2868068218231201s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020323514938354492s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.799003601074219e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-sider took 5.0131471157073975s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7036631107330322s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2863008975982666s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.843971252441406e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.560803651809692s
Availability | SPARQL endpoint availability check for fvdb took 4.124641418457031e-05s
Availability | VoID file availability check for fvdb took 0.0010828971862792969s
Completeness | Calculation of interlinking completeness for fvdb took 0.27774620056152344s
Reputation | Calculation of the PageRank for fvdb took 0.02096700668334961s
Interlinking | Calculation of Degree of Connection for fvdb took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0008347034454345703s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.409385681152344e-05s
Believability | Calculation of trust value for fvdb took 7.152557373046875e-06s
INFO | --- Analysis for fv took 12.548573970794678s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.220008850097656e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0007524490356445312s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.26838135719299316s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020332813262939453s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.9325485229492188e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.3909759521484375e-06s
INFO | --- Analysis for GACS took 3.6479604244232178s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.100799560546875e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.2732253074645996s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.02021026611328125s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.0279159545898438e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 8.106231689453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 3.048079013824463s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.076957702636719e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.3009040355682373s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020293474197387695s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.838539123535156e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 6.67572021484375e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.4613940715789795s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.0531158447265625e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0010907649993896484s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.2736375331878662s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.894371032714844e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.152557373046875e-06s
INFO | --- Analysis for garnicaplywood took 3.1189615726470947s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.0531158447265625e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.29370808601379395s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.465217590332031e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.58306884765625e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 6.954828500747681s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.31349897384643555s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2709519863128662s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.059906005859375e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.7404556274414062e-05s
INFO | --- Analysis for gemet took 4.686989068984985s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.076957702636719e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.287139892578125s
Reputation | Calculation of the PageRank for gemet-annotated took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.838539123535156e-05s
Believability | Calculation of trust value for gemet-annotated took 8.106231689453125e-06s
INFO | --- Analysis for gemet-annotated took 3.1566970348358154s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 1.069218635559082s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.27492499351501465s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.838539123535156e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 6.9141387939453125e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.610960960388184s
Availability | SPARQL endpoint availability check for Super Ontology took 0.727869987487793s
Availability | VoID file availability check for Super Ontology took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2889120578765869s
Reputation | Calculation of the PageRank for Super Ontology took 0.02007770538330078s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 5.125999450683594e-05s
Believability | Calculation of trust value for Super Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 4.070671319961548s
Availability | SPARQL endpoint availability check for geo.place took 4.315376281738281e-05s
Availability | VoID file availability check for geo.place took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for geo.place took 0.26178550720214844s
Reputation | Calculation of the PageRank for geo.place took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for geo.place took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for geo.place took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for geo.place took 4.863739013671875e-05s
Believability | Calculation of trust value for geo.place took 7.62939453125e-06s
INFO | --- Analysis for geo_place took 3.077540636062622s
Availability | SPARQL endpoint availability check for Geographic detector model took 6.0558319091796875e-05s
Availability | VoID file availability check for Geographic detector model took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.2892429828643799s
Reputation | Calculation of the PageRank for Geographic detector model took 0.0202786922454834s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.075599670410156e-05s
Believability | Calculation of trust value for Geographic detector model took 7.152557373046875e-06s
INFO | --- Analysis for GeoDetector took 13.817793846130371s
Availability | SPARQL endpoint availability check for geodomainwn took 4.1961669921875e-05s
Availability | VoID file availability check for geodomainwn took 0.0010938644409179688s
Completeness | Calculation of interlinking completeness for geodomainwn took 1.0614769458770752s
Reputation | Calculation of the PageRank for geodomainwn took 0.0213468074798584s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.650520324707031e-05s
Believability | Calculation of trust value for geodomainwn took 6.9141387939453125e-06s
INFO | --- Analysis for geodomainwn took 967.6601226329803s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.1484832763671875e-05s
Availability | VoID file availability check for GeoEcuador took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2928628921508789s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.508827209472656e-05s
Believability | Calculation of trust value for GeoEcuador took 7.62939453125e-06s
INFO | --- Analysis for geoecuador took 14.630883693695068s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.4016146659851074s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.30414271354675293s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02011561393737793s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.389617919921875e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 6.67572021484375e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 48.87530016899109s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.29935312271118164s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.0040740966796875e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.152557373046875e-06s
INFO | --- Analysis for geographic-openuplabs took 4.671918153762817s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5864753723144531s
Availability | VoID file availability check for GeoLinkedData took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.3100299835205078s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020077228546142578s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 9.083747863769531e-05s
Believability | Calculation of trust value for GeoLinkedData took 6.198883056640625e-06s
INFO | --- Analysis for geolinkeddata took 5.7938926219940186s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.9827113151550293s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.7217285633087158s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.130073547363281e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 7.413741827011108s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.1484832763671875e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.3039286136627197s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.0202484130859375s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0010466575622558594s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0006039142608642578s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.152557373046875e-06s
INFO | --- Analysis for geonames-semantic-web took 3.6702287197113037s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.172325134277344e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.7389628887176514s
Reputation | Calculation of the PageRank for Geospatial World  took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010371208190917969s
Believability | Calculation of trust value for Geospatial World  took 8.58306884765625e-06s
INFO | --- Analysis for geospatialworld-net took 3.7049648761749268s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.6442875862121582s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.30096006393432617s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00014138221740722656s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 8.344650268554688e-06s
INFO | --- Analysis for geospecies took 6.356044054031372s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.124641418457031e-05s
Availability | VoID file availability check for GeoWordNet took 0.0007419586181640625s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2961850166320801s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.030632019042969e-05s
Believability | Calculation of trust value for GeoWordNet took 7.867813110351562e-06s
INFO | --- Analysis for geowordnet took 7.907331943511963s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.17393064498901367s
Availability | VoID file availability check for German labor law thesaurus took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.2947425842285156s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.0108642578125e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.62939453125e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.8925275802612305s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 5.2928924560546875e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.3229830265045166s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02113056182861328s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.935264587402344e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 9.775161743164062e-06s
INFO | --- Analysis for germlex took 2.9179530143737793s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.6971971988677979s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.30293965339660645s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.1552734375e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.58306884765625e-06s
INFO | --- Analysis for gesis-thesoz took 6.6015684604644775s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.7972118854522705s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.3045210838317871s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.581710815429688e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 8.821487426757812e-06s
INFO | --- Analysis for getty-aat took 25.30972695350647s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 2.4931042194366455s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.30734705924987793s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.02071547508239746s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.3882598876953125e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 6.4373016357421875e-06s
INFO | --- Analysis for getty-tgn took 23.777567625045776s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.30672359466552734s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.3115816116333008s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.170967102050781e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.7220458984375e-06s
INFO | --- Analysis for gipuzkoademografia took 8.229793071746826s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.100799560546875e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.3019866943359375s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.075599670410156e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 7.867813110351562e-06s
INFO | --- Analysis for glastonbury-2011 took 7.403338432312012s
Availability | SPARQL endpoint availability check for Global Change Information System took 5.626678466796875e-05s
Availability | VoID file availability check for Global Change Information System took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.32666850090026855s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020447969436645508s
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.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 4.76837158203125e-05s
Believability | Calculation of trust value for Global Change Information System took 6.67572021484375e-06s
INFO | --- Analysis for global-change-information-system took 3.404665946960449s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.2438507080078125e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.29268836975097656s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020287513732910156s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.839897155761719e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.67572021484375e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.424358367919922s
Availability | SPARQL endpoint availability check for Glottolog took 5.316734313964844e-05s
Availability | VoID file availability check for Glottolog took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2981271743774414s
Reputation | Calculation of the PageRank for Glottolog took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.0067901611328125e-05s
Believability | Calculation of trust value for Glottolog took 7.867813110351562e-06s
INFO | --- Analysis for glottolog took 7.782181978225708s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.100799560546875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.302997350692749s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0009884834289550781s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.0001239776611328125s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 7.867813110351562e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 7.061785459518433s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.1484832763671875e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.2899003028869629s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 3.0040740966796875e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 8.106231689453125e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 3.264025926589966s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.1484832763671875e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.2904067039489746s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.123283386230469e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 7.62939453125e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 3.289285898208618s
Availability | SPARQL endpoint availability check for 1121 took 4.124641418457031e-05s
Availability | VoID file availability check for 1121 took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for 1121 took 0.32548093795776367s
Reputation | Calculation of the PageRank for 1121 took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for 1121 took 2.9087066650390625e-05s
Believability | Calculation of trust value for 1121 took 8.106231689453125e-06s
INFO | --- Analysis for God_ took 3.468628168106079s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 7.295608520507812e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2946035861968994s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020392656326293945s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.030632019042969e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 7.867813110351562e-06s
INFO | --- Analysis for gold took 4.589092493057251s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.2438507080078125e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.29614758491516113s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.699562072753906e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 7.3909759521484375e-06s
INFO | --- Analysis for googleart-wrapper took 3.0061733722686768s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.10491204261779785s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.30452466011047363s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.123283386230469e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 6.9141387939453125e-06s
INFO | --- Analysis for govagribus-denmark took 34.875462770462036s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.5538885593414307s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.3380560874938965s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0008614063262939453s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 9.083747863769531e-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 24.437150716781616s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 2.430715322494507s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2929103374481201s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020058155059814453s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.344650268554688e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.9604644775390625e-06s
INFO | --- Analysis for govtrack took 12.587591886520386s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.1961669921875e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.30623698234558105s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.936622619628906e-05s
Believability | Calculation of trust value for greek-administrative-geography took 7.152557373046875e-06s
INFO | --- Analysis for greek-administrative-geography took 3.3627777099609375s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.27822113037109375s
Availability | VoID file availability check for Greek Wordnet took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2925105094909668s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 3.8623809814453125e-05s
Believability | Calculation of trust value for Greek Wordnet took 8.821487426757812e-06s
INFO | --- Analysis for greek-wordnet took 3.008430004119873s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 2.934518337249756s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.3226501941680908s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.1682510375976562e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 7.867813110351562e-06s
INFO | --- Analysis for greek_prisons_releases took 56.63013195991516s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.8065049648284912s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3234541416168213s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.605552673339844e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.198883056640625e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.8959126472473145s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.076957702636719e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.3036527633666992s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0006985664367675781s
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 5.187637805938721s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 2.03535795211792s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.3115274906158447s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.673004150390625e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 6.198883056640625e-06s
INFO | --- Analysis for grrp took 4.857850790023804s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.655177116394043s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.3128688335418701s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.651878356933594e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.7220458984375e-06s
INFO | --- Analysis for grrt took 4.443354606628418s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.533616304397583s
Availability | VoID file availability check for Geological Timescale took 0.0005972385406494141s
Extra | Recovery of all triples for Geological Timescale took 2.146542549133301s
Performance | Total latancy measurement for Geological Timescale took 3.775482416152954s
Amount of data | Number of triples check for Geological Timescale took 0.47676873207092285s
Interoperability | New terms check for Geological Timescale took 1.6268763542175293s
Versatility | Languages check for Geological Timescale took 0.5141775608062744s
Interpretability | Number of blank nodes check for Geological Timescale took 1.0415048599243164s
Security | Check HTTPS for Geological Timescale took 0.3721742630004883s
Interpretability | RDF structures check for Geological Timescale took 0.9522190093994141s
Versatility | Serialization formats check for Geological Timescale took 0.41824841499328613s
Availability | RDF dump link check for Geological Timescale took 1.2092037200927734s
License | MR license check for Geological Timescale took 0.434476375579834s
License | HR license check for Geological Timescale took 0.45319390296936035s
Amount of data | Number of property check for Geological Timescale took 0.42196202278137207s
Understandability | Number of label check for Geological Timescale took 0.45806074142456055s
Understandability | URI regex check for Geological Timescale took 0.8610134124755859s
Understandability | Vocabs check for Geological Timescale took 0.43164944648742676s
Verifiability | Authors check for Geological Timescale took 0.9619202613830566s
Verifiability | Publishers check for Geological Timescale took 0.44953441619873047s
Performance | Throughput check for Geological Timescale took 15.636795282363892s
Amount of data | Check the number of entities for Geological Timescale took 0.024840116500854492s
Verifiability | Contribs. check for Geological Timescale took 0.9738943576812744s
Interlinking | sameAs chians check for Geological Timescale took 0.9673326015472412s
Interlinking | skos check for Geological Timescale took 0.9659454822540283s
Interlinking | skos check for Geological Timescale took 0.4250195026397705s
Timeliness | dataset update frequency check for Geological Timescale took 0.4578583240509033s
Currency | Creation date check for Geological Timescale took 1.3931050300598145s
Currency | Modification date check for Geological Timescale took 0.9889822006225586s
Rep.Conc. | URIs length for Geological Timescale took 2.132068634033203s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.9498941898345947s
Accuracy | Check Functional Property for Geological Timescale took 0.9939844608306885s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.4268646240234375s
Accuracy | Check Empty annotation labels for Geological Timescale took 0.8350424766540527s
Accuracy | Check White space in annotation for Geological Timescale took 0.0156402587890625s
Accuracy | Check Datatype consistency for Geological Timescale took 0.0757133960723877s
Consistency | Disjoint class check for Geological Timescale took 0.4222896099090576s
Consistency | Check Misplaced properties for Geological Timescale took 3.0123369693756104s
Consistency | Misplaced classes for Geological Timescale took 0.554685115814209s
Consistency | Check Ontology hijacking for Geological Timescale took 1.6789500713348389s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1826119422912598s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.1918013095855713s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.052498579025268555s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.42711949348449707s
Security | Sign check for Geological Timescale took 0.4263777732849121s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.958425760269165s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.30734944343566895s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.152557373046875e-05s
Believability | Calculation of trust value for Geological Timescale took 8.58306884765625e-06s
INFO | --- Analysis for GTS took 105.86472296714783s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.29491353034973145s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for GTS-ont took 2.9407172203063965s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.553794860839844e-05s
Availability | VoID file availability check for GUTSTOK  took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.29013609886169434s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020748138427734375s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.123283386230469e-05s
Believability | Calculation of trust value for GUTSTOK  took 7.152557373046875e-06s
INFO | --- Analysis for Guillaume_Forget took 2.6771910190582275s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.1484832763671875e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0007715225219726562s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.30678844451904297s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.67572021484375e-05s
Believability | Calculation of trust value for Project Gutenberg took 7.62939453125e-06s
INFO | --- Analysis for gutenberg took 9.599002599716187s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.1484832763671875e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.31703829765319824s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.838539123535156e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 6.67572021484375e-06s
INFO | --- Analysis for gwa-ili took 5.7452712059021s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.291534423828125e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.30755162239074707s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.170967102050781e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 6.67572021484375e-06s
INFO | --- Analysis for GWR took 13.890328168869019s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.0531158447265625e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.3012659549713135s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020192623138427734s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.075599670410156e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 6.4373016357421875e-06s
INFO | --- Analysis for HASM took 10.591629028320312s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 7.152557373046875e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.3176760673522949s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.075599670410156e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for hcls-knowledge-base took 3.3019511699676514s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.1720540523529053s
Availability | VoID file availability check for HealthCare Ontology took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.295992374420166s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.719329833984375e-05s
Believability | Calculation of trust value for HealthCare Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for HealthCare_Ontology took 6.3467793464660645s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.172325134277344e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.31421613693237305s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.246566772460938e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 8.106231689453125e-06s
INFO | --- Analysis for heartfailure took 3.207937479019165s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.855506896972656s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.3649139404296875s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.7670135498046875e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 7.152557373046875e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 120.2016065120697s
Availability | SPARQL endpoint availability check for Hedatuz took 0.27536535263061523s
Availability | VoID file availability check for Hedatuz took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.29670071601867676s
Reputation | Calculation of the PageRank for Hedatuz took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.9577484130859375e-05s
Believability | Calculation of trust value for Hedatuz took 8.344650268554688e-06s
INFO | --- Analysis for hedatuz took 3.7747130393981934s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.14278459548950195s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2971484661102295s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.0001266002655029297s
Believability | Calculation of trust value for Hellenic Fire Brigade took 6.67572021484375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.886975049972534s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.021245718002319336s
Availability | VoID file availability check for Hellenic Police took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.30930328369140625s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00013113021850585938s
Believability | Calculation of trust value for Hellenic Police took 6.4373016357421875e-06s
INFO | --- Analysis for hellenic-police took 2.831406593322754s
Availability | SPARQL endpoint availability check for Hermos took 4.1961669921875e-05s
Availability | VoID file availability check for Hermos took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Hermos took 0.31219983100891113s
Reputation | Calculation of the PageRank for Hermos took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for Hermos took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hermos took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.170967102050781e-05s
Believability | Calculation of trust value for Hermos took 8.106231689453125e-06s
INFO | --- Analysis for Hermos took 3.2624571323394775s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.410743713378906e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2983510494232178s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.1948089599609375e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 8.58306884765625e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.7363953590393066s
Availability | SPARQL endpoint availability check for HITO took 0.45469212532043457s
Availability | VoID file availability check for HITO took 0.0005533695220947266s
Extra | Recovery of all triples for HITO took 3.402338743209839s
Performance | Total latancy measurement for HITO took 1.0393507480621338s
Amount of data | Number of triples check for HITO took 0.20951533317565918s
Interoperability | New terms check for HITO took 1.428910493850708s
Versatility | Languages check for HITO took 0.22200417518615723s
Interpretability | Number of blank nodes check for HITO took 0.21792840957641602s
Interpretability | RDF structures check for HITO took 0.20949459075927734s
Versatility | Serialization formats check for HITO took 0.20870423316955566s
Availability | RDF dump link check for HITO took 0.20897150039672852s
License | MR license check for HITO took 0.20916342735290527s
License | HR license check for HITO took 0.22797060012817383s
Amount of data | Number of property check for HITO took 0.21167564392089844s
Understandability | Number of label check for HITO took 0.2157115936279297s
Understandability | URI regex check for HITO took 0.4204065799713135s
Understandability | Vocabs check for HITO took 0.20621347427368164s
Verifiability | Authors check for HITO took 0.20734071731567383s
Verifiability | Publishers check for HITO took 0.20826172828674316s
Performance | Throughput check for HITO took 10.439940690994263s
Amount of data | Check the number of entities for HITO took 6.794929504394531e-05s
Verifiability | Contribs. check for HITO took 0.2067251205444336s
Interlinking | sameAs chians check for HITO took 0.20694684982299805s
Interlinking | skos check for HITO took 0.23238897323608398s
Interlinking | skos check for HITO took 0.20787382125854492s
Timeliness | dataset update frequency check for HITO took 0.20839858055114746s
Currency | Creation date check for HITO took 0.41915345191955566s
Currency | Modification date check for HITO took 0.4171900749206543s
Rep.Conc. | URIs length for HITO took 1.2815423011779785s
Interoperability | New vocabularies check for HITO took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.20756816864013672s
Accuracy | Check Functional Property for HITO took 0.20819306373596191s
Accuracy | Check Inverse Functional Property for HITO took 0.2082056999206543s
Accuracy | Check Empty annotation labels for HITO took 0.602881908416748s
Accuracy | Check White space in annotation for HITO took 0.012900114059448242s
Accuracy | Check Datatype consistency for HITO took 0.07106757164001465s
Consistency | Disjoint class check for HITO took 0.20689702033996582s
Consistency | Check Misplaced properties for HITO took 0.5495398044586182s
Consistency | Misplaced classes for HITO took 0.37396717071533203s
Consistency | Check Ontology hijacking for HITO took 1.6884808540344238s
Consistency | Check Invalid usage of undefined classes for HITO took 1.1913917064666748s
Consistency | Check Invalid usage of undefined properties for HITO took 1.4626953601837158s
Conciseness | Check Extensional conciseness for HITO took 0.06146883964538574s
Conciseness | Check Intensional conciseness for HITO took 0.20515942573547363s
Security | Sign check for HITO took 0.2088017463684082s
Availability | Check URIs Dereferenciability for HITO took 1775.9107313156128s
Completeness | Calculation of interlinking completeness for HITO took 1.6729655265808105s
Reputation | Calculation of the PageRank for HITO took 0.024479389190673828s
Interlinking | Calculation of Degree of Connection for HITO took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for HITO took 8.058547973632812e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.430511474609375e-06s
Believability | Calculation of trust value for HITO took 6.9141387939453125e-06s
INFO | --- Analysis for hito took 1829.876318693161s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 9.35373568534851s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.28143882751464844s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 2.8371810913085938e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 6.9141387939453125e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 44.67705726623535s
Availability | SPARQL endpoint availability check for Homologene took 4.029273986816406e-05s
Availability | VoID file availability check for Homologene took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Homologene took 0.7117908000946045s
Reputation | Calculation of the PageRank for Homologene took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for Homologene took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Homologene took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.4809112548828125e-05s
Believability | Calculation of trust value for Homologene took 7.62939453125e-06s
INFO | --- Analysis for homologene took 4.3926682472229s
Availability | SPARQL endpoint availability check for gseg took 4.4345855712890625e-05s
Availability | VoID file availability check for gseg took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for gseg took 0.8047246932983398s
Reputation | Calculation of the PageRank for gseg took 0.02117609977722168s
Interlinking | Calculation of Degree of Connection for gseg took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for gseg took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for gseg took 3.361701965332031e-05s
Believability | Calculation of trust value for gseg took 8.106231689453125e-06s
INFO | --- Analysis for hongse took 4.465888261795044s
Availability | SPARQL endpoint availability check for Noticias Universia took 3.9577484130859375e-05s
Availability | VoID file availability check for Noticias Universia took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.2913362979888916s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.314018249511719e-05s
Believability | Calculation of trust value for Noticias Universia took 7.867813110351562e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 3.1107656955718994s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.172325134277344e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.7164623737335205s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.0994415283203125e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.33514404296875e-05s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 4.5197930335998535s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.7210633754730225s
Availability | VoID file availability check for COURAGE Dataset took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.3033933639526367s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.02011847496032715s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for COURAGE Dataset took 8.106231689453125e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 7.321419715881348s
Availability | SPARQL endpoint availability check for RoadTrb took 4.172325134277344e-05s
Availability | VoID file availability check for RoadTrb took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.276261568069458s
Reputation | Calculation of the PageRank for RoadTrb took 0.031554460525512695s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0012066364288330078s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 4.863739013671875e-05s
Believability | Calculation of trust value for RoadTrb took 9.059906005859375e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.643460273742676s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.27215147018432617s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.867813110351562e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 24.84861397743225s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 7.677078247070312e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.26956772804260254s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.123283386230469e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 9.059906005859375e-06s
INFO | --- Analysis for http:pakistan.com took 2.527266025543213s
Availability | SPARQL endpoint availability check for CEDICT took 4.1484832763671875e-05s
Availability | VoID file availability check for CEDICT took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for CEDICT took 0.2958719730377197s
Reputation | Calculation of the PageRank for CEDICT took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.123283386230469e-05s
Believability | Calculation of trust value for CEDICT took 6.67572021484375e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.682352542877197s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.5421335697174072s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2712576389312744s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.915496826171875e-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.755765438079834s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.1961669921875e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2880520820617676s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.0251998901367188e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 3.0611789226531982s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.315376281738281e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.2597179412841797s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.2901763916015625e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.533005475997925s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.00543212890625e-05s
Availability | VoID file availability check for Soccer Dataset took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.3017089366912842s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020760536193847656s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for Soccer Dataset took 6.67572021484375e-06s
INFO | --- Analysis for http:www.msm.com took 2.6026368141174316s
Availability | SPARQL endpoint availability check for Game Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Game Ontology took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.2833902835845947s
Reputation | Calculation of the PageRank for Game Ontology took 0.02138805389404297s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.8623809814453125e-05s
Believability | Calculation of trust value for Game Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.0763707160949707s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.172325134277344e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2866220474243164s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.266334533691406e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.344650268554688e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.265146017074585s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.267692565917969e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.29152655601501465s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02071356773376465s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.147125244140625e-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.530442237854004s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.124641418457031e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0003674030303955078s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2988765239715576s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.314018249511719e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.538475751876831s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.220008850097656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2623136043548584s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.123283386230469e-05s
Believability | Calculation of trust value for Indian Biodiversity took 8.344650268554688e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.528391122817993s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.124641418457031e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.29225635528564453s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.24249267578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 8.344650268554688e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.6314265727996826s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.100799560546875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.30941319465637207s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.361701965332031e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.198883056640625e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.6803956031799316s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.4345855712890625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.27866625785827637s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.4332275390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 8.106231689453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.530921459197998s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.363059997558594e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.2894148826599121s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.147125244140625e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 7.867813110351562e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 3.9233086109161377s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.1714482307434082s
Availability | VoID file availability check for Bookkeeping took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.29421544075012207s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020172595977783203s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bookkeeping took 8.106231689453125e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.227663993835449s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Legal Ontology took 0.00038504600524902344s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.2861752510070801s
Reputation | Calculation of the PageRank for Legal Ontology took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0009989738464355469s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 4.220008850097656e-05s
Believability | Calculation of trust value for Legal Ontology took 8.344650268554688e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 3.12011456489563s
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.0006506443023681641s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.29435038566589355s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.700920104980469e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 5.9604644775390625e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 11.974193334579468s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.220008850097656e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.30164551734924316s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.021273374557495117s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.0040740966796875e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 6.9141387939453125e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.736316204071045s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.1961669921875e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.32205915451049805s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.147125244140625e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 8.821487426757812e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 3.0820865631103516s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 3.9577484130859375e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2801849842071533s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.123283386230469e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 8.821487426757812e-06s
INFO | --- Analysis for hud-library-usagedata took 3.020925283432007s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.579559087753296s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.2757997512817383s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010442733764648438s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 6.9141387939453125e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.515998363494873s
Availability | SPARQL endpoint availability check for IATE RDF took 4.291534423828125e-05s
Availability | VoID file availability check for IATE RDF took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2548835277557373s
Reputation | Calculation of the PageRank for IATE RDF took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for IATE RDF took 9.059906005859375e-06s
INFO | --- Analysis for iate-rdf took 2.783001661300659s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 0.8051400184631348s
Availability | VoID file availability check for IATI as Linked Data took 0.0007224082946777344s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.27686190605163574s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 9.012222290039062e-05s
Believability | Calculation of trust value for IATI as Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for iati-as-linked-data took 8.19549560546875s
Availability | SPARQL endpoint availability check for ICANE took 0.355421781539917s
Availability | VoID file availability check for ICANE took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for ICANE took 0.2843015193939209s
Reputation | Calculation of the PageRank for ICANE took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for ICANE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.678436279296875e-05s
Believability | Calculation of trust value for ICANE took 5.9604644775390625e-06s
INFO | --- Analysis for icane took 3.8326356410980225s
Availability | SPARQL endpoint availability check for ichoose took 0.1639242172241211s
Availability | VoID file availability check for ichoose took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for ichoose took 0.2687511444091797s
Reputation | Calculation of the PageRank for ichoose took 0.021230697631835938s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.937980651855469e-05s
Believability | Calculation of trust value for ichoose took 6.67572021484375e-06s
INFO | --- Analysis for ichoose took 43.97196435928345s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 1.0428433418273926s
Availability | VoID file availability check for The Iconology Dataset took 0.0006611347198486328s
Extra | Recovery of all triples for The Iconology Dataset took 5.433091878890991s
Performance | Total latancy measurement for The Iconology Dataset took 0.6466896533966064s
Amount of data | Number of triples check for The Iconology Dataset took 0.22643136978149414s
Interoperability | New terms check for The Iconology Dataset took 1.3447203636169434s
Versatility | Languages check for The Iconology Dataset took 0.5364141464233398s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.19021296501159668s
Interpretability | RDF structures check for The Iconology Dataset took 0.1312558650970459s
Versatility | Serialization formats check for The Iconology Dataset took 0.11292099952697754s
Availability | RDF dump link check for The Iconology Dataset took 0.09929180145263672s
License | MR license check for The Iconology Dataset took 0.11103129386901855s
License | HR license check for The Iconology Dataset took 0.33611631393432617s
Amount of data | Number of property check for The Iconology Dataset took 0.1069793701171875s
Understandability | Number of label check for The Iconology Dataset took 0.15384149551391602s
Understandability | URI regex check for The Iconology Dataset took 0.1693263053894043s
Understandability | Vocabs check for The Iconology Dataset took 0.09151601791381836s
Verifiability | Authors check for The Iconology Dataset took 0.10259175300598145s
Verifiability | Publishers check for The Iconology Dataset took 0.08953595161437988s
Performance | Throughput check for The Iconology Dataset took 10.474602460861206s
Amount of data | Check the number of entities for The Iconology Dataset took 0.00012373924255371094s
Verifiability | Contribs. check for The Iconology Dataset took 0.0886542797088623s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09476900100708008s
Interlinking | skos check for The Iconology Dataset took 0.08999466896057129s
Interlinking | skos check for The Iconology Dataset took 0.08538055419921875s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08974385261535645s
Currency | Creation date check for The Iconology Dataset took 0.18375205993652344s
Currency | Modification date check for The Iconology Dataset took 0.19468092918395996s
Rep.Conc. | URIs length for The Iconology Dataset took 1.3662843704223633s
Interoperability | New vocabularies check for The Iconology Dataset took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.0835416316986084s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.33733320236206055s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.01617717742919922s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.4342970848083496s
Consistency | Disjoint class check for The Iconology Dataset took 0.0850977897644043s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15442681312561035s
Consistency | Misplaced classes for The Iconology Dataset took 0.89300537109375s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.527500867843628s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.1931018829345703s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.2724266052246094s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.30184149742126465s
Security | Sign check for The Iconology Dataset took 0.08367919921875s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2532.8724415302277s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.473581314086914s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.027737140655517578s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.4543533325195312e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 8.344650268554688e-06s
INFO | --- Analysis for iconology-dataset took 2594.668317079544s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.0531158447265625e-05s
Availability | VoID file availability check for Identifiers.org took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.2955172061920166s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020302772521972656s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.8623809814453125e-05s
Believability | Calculation of trust value for Identifiers.org took 7.62939453125e-06s
INFO | --- Analysis for identifiers-org took 4.450038909912109s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.0531158447265625e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.26001906394958496s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.772445678710938e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 6.4373016357421875e-06s
INFO | --- Analysis for idreffr took 5.041324138641357s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.9201598167419434s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.3014209270477295s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.078315734863281e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 9.059906005859375e-06s
INFO | --- Analysis for ids took 5.23499321937561s
Availability | SPARQL endpoint availability check for ietflang took 7.343292236328125e-05s
Availability | VoID file availability check for ietflang took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for ietflang took 0.28322768211364746s
Reputation | Calculation of the PageRank for ietflang took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for ietflang took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.792213439941406e-05s
Believability | Calculation of trust value for ietflang took 8.58306884765625e-06s
INFO | --- Analysis for ietflang took 13.173587560653687s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.5292642116546631s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.27949953079223633s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 4.100799560546875e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for IGVLL took 4.557720899581909s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.45009708404541016s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0006067752838134766s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.8798155784606934s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9792430400848389s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.18467450141906738s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.3550665378570557s
Versatility | Languages check for 3LGM² IHE Ontology took 0.20363998413085938s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.20495080947875977s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.20469427108764648s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.1997389793395996s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.2061140537261963s
License | MR license check for 3LGM² IHE Ontology took 0.20989704132080078s
License | HR license check for 3LGM² IHE Ontology took 0.20224285125732422s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.19848084449768066s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.20121192932128906s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.3833341598510742s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.19608187675476074s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.1847531795501709s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.1869206428527832s
Performance | Throughput check for 3LGM² IHE Ontology took 11.236856937408447s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.128715515136719e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.19576239585876465s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.19738078117370605s
Interlinking | skos check for 3LGM² IHE Ontology took 0.19836115837097168s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1965312957763672s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.20943164825439453s
Currency | Creation date check for 3LGM² IHE Ontology took 0.39584994316101074s
Currency | Modification date check for 3LGM² IHE Ontology took 0.4039738178253174s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8546643257141113s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.1950547695159912s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.19684600830078125s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.19731807708740234s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.33389997482299805s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0018126964569091797s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.04911184310913086s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.1947023868560791s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4447288513183594s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.28408217430114746s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.4800376892089844s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.1711137294769287s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.451406478881836s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.033225297927856445s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.19826626777648926s
Security | Sign check for 3LGM² IHE Ontology took 0.21127891540527344s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 390.0031912326813s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.8326294422149658s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.021140575408935547s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 8.749961853027344e-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.106231689453125e-06s
INFO | --- Analysis for IHE took 436.5711233615875s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.07171249389648438s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.2904200553894043s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 2.9325485229492188e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 8.106231689453125e-06s
INFO | --- Analysis for iislod-test took 3.072451591491699s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.100799560546875e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.7380857467651367s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.0040740966796875e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 7.152557373046875e-06s
INFO | --- Analysis for ILUSOC took 13.621841669082642s
Availability | SPARQL endpoint availability check for im@sparql took 5.961558818817139s
Availability | VoID file availability check for im@sparql took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for im@sparql took 0.2782258987426758s
Reputation | Calculation of the PageRank for im@sparql took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.8848648071289062e-05s
Believability | Calculation of trust value for im@sparql took 7.867813110351562e-06s
INFO | --- Analysis for im@sparql took 13.348688840866089s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.1961669921875e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0004131793975830078s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2816941738128662s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 2.956390380859375e-05s
Believability | Calculation of trust value for imagery bailingniao took 3.504753112792969e-05s
INFO | --- Analysis for imagery_bailingniao took 3.429180383682251s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.128462553024292s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.00044536590576171875s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 25.970173835754395s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.480116367340088s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.11702275276184s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.2675230503082275s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.72214651107788s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 7.770487070083618s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.675844669342041s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7378489971160889s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7733373641967773s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7756185531616211s
License | MR license check for Imagesnippets Image Descriptions took 0.7447803020477295s
License | HR license check for Imagesnippets Image Descriptions took 10.763622999191284s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.6677632331848145s
Understandability | Number of label check for Imagesnippets Image Descriptions took 3.2408242225646973s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.394273281097412s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7141730785369873s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7068097591400146s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7212049961090088s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.885534524917603s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.62939453125e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7537577152252197s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7543163299560547s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7165205478668213s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7100117206573486s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6940624713897705s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.5109927654266357s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.490309715270996s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 29.590303897857666s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7397308349609375s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6769697666168213s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7039511203765869s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.6970751285552979s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.7059876918792725s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 16.92827033996582s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.169734239578247s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00016117095947265625s
Security | Sign check for Imagesnippets Image Descriptions took 0.7149429321289062s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.7371313571929932s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.417533874511719e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.6689300537109375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 7.867813110351562e-06s
INFO | --- Analysis for imagesnippets took 262.6818506717682s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.5427649021148682s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.28939056396484375s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.393692016601562e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for imf-linked-data took 4.457122325897217s
Availability | SPARQL endpoint availability check for IMGpedia took 4.315376281738281e-05s
Availability | VoID file availability check for IMGpedia took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.26955199241638184s
Reputation | Calculation of the PageRank for IMGpedia took 0.020707130432128906s
Interlinking | Calculation of Degree of Connection for IMGpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.24249267578125e-05s
Believability | Calculation of trust value for IMGpedia took 8.106231689453125e-06s
INFO | --- Analysis for imgpedia took 4.6544811725616455s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 3.9577484130859375e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.2901651859283447s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.86102294921875e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 7.152557373046875e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 3.0764269828796387s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.172325134277344e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.2707827091217041s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1444091796875e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 6.67572021484375e-06s
INFO | --- Analysis for Imtiaz took 2.4283714294433594s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.172325134277344e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0008516311645507812s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2780323028564453s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.147125244140625e-05s
Believability | Calculation of trust value for Royalty Free Music took 7.3909759521484375e-06s
INFO | --- Analysis for inaudio.org took 4.086542844772339s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.172325134277344e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2772254943847656s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020890235900878906s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.075599670410156e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 8.821487426757812e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 3.2906177043914795s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.029273986816406e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.34412550926208496s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007431507110595703s
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 3.816474676132202s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.4199657440185547s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.30069446563720703s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 6.198883056640625e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 4.259842157363892s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.3392181396484375e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.3019595146179199s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.218650817871094e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 8.344650268554688e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 3.104013681411743s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.3392181396484375e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.000762939453125s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.26102352142333984s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010704994201660156s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 9.059906005859375e-06s
INFO | --- Analysis for ineverycrea took 19.666763067245483s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.1961669921875e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.000774383544921875s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2664163112640381s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020415067672729492s
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.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.465217590332031e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.821487426757812e-06s
INFO | --- Analysis for ineverycrea-argentina took 10.851598739624023s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 523.101922750473s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.7084462642669678s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.033348083496094e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for influence-tracker-dataset took 1082.423688173294s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.363059997558594e-05s
Availability | VoID file availability check for INSEMTIVES took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.2955615520477295s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.910064697265625e-05s
Believability | Calculation of trust value for INSEMTIVES took 6.67572021484375e-06s
INFO | --- Analysis for insemtives took 5.106785297393799s
Availability | SPARQL endpoint availability check for instagram.person took 4.0531158447265625e-05s
Availability | VoID file availability check for instagram.person took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for instagram.person took 0.3055896759033203s
Reputation | Calculation of the PageRank for instagram.person took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.1948089599609375e-05s
Believability | Calculation of trust value for instagram.person took 7.152557373046875e-06s
INFO | --- Analysis for instagram_person took 4.469864845275879s
Availability | SPARQL endpoint availability check for instagram.videoobject took 3.933906555175781e-05s
Availability | VoID file availability check for instagram.videoobject took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.26082706451416016s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.170967102050781e-05s
Believability | Calculation of trust value for instagram.videoobject took 6.67572021484375e-06s
INFO | --- Analysis for instagram_videoobject took 3.5167503356933594s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.29833984375s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020934104919433594s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.2901763916015625e-05s
Believability | Calculation of trust value for Instance Hub Countries took 9.059906005859375e-06s
INFO | --- Analysis for instance-hub-countries took 3.528114080429077s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.30908846855163574s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.571255922317505s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.315376281738281e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.28311610221862793s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020721912384033203s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.1948089599609375e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-organizations took 3.5832221508026123s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub People took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.3274407386779785s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.2901763916015625e-05s
Believability | Calculation of trust value for Instance Hub People took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-people took 3.3502228260040283s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 3.910064697265625e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.3213376998901367s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.1948089599609375e-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 3.5024807453155518s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.00543212890625e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.30670619010925293s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 3.41072416305542s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.1961669921875e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.30176663398742676s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020766496658325195s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.0517578125e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 3.3750686645507812s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.00543212890625e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.26839590072631836s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.170967102050781e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-crops took 5.221014976501465s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 3.981590270996094e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2610056400299072s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.075599670410156e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 3.1149871349334717s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.291534423828125e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.3009490966796875s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.02212691307067871s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.337860107421875e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 3.0645649433135986s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.300431489944458s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 3.167975902557373s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.9577484130859375e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.2973825931549072s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.0517578125e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.62939453125e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 3.1217868328094482s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.506111145019531e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0003342628479003906s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.2842850685119629s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020235538482666016s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.751319885253906e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for interactivemaps-gnoss took 11.821829080581665s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 5.412101745605469e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2917304039001465s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 2.956390380859375e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 7.62939453125e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 3.1290462017059326s
Availability | SPARQL endpoint availability check for intervalue took 0.2474536895751953s
Availability | VoID file availability check for intervalue took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for intervalue took 0.2914698123931885s
Reputation | Calculation of the PageRank for intervalue took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for intervalue took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for intervalue took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.580352783203125e-05s
Believability | Calculation of trust value for intervalue took 6.67572021484375e-06s
INFO | --- Analysis for intervalue took 2.7741951942443848s
Availability | SPARQL endpoint availability check for Inztrow took 4.124641418457031e-05s
Availability | VoID file availability check for Inztrow took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2810828685760498s
Reputation | Calculation of the PageRank for Inztrow took 0.020182132720947266s
Interlinking | Calculation of Degree of Connection for Inztrow took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Inztrow took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.7894973754882812e-05s
Believability | Calculation of trust value for Inztrow took 6.67572021484375e-06s
INFO | --- Analysis for Inztrow took 3.884436845779419s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.28420352935791016s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 5.7220458984375e-06s
INFO | --- Analysis for ipbes took 4.145066976547241s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.124641418457031e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2756175994873047s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 3.9577484130859375e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 6.9141387939453125e-06s
INFO | --- Analysis for iptc-newscodes took 3.644453287124634s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.9577484130859375e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.27961063385009766s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 2.765655517578125e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 7.152557373046875e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 3.0365748405456543s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 7.715104579925537s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2860240936279297s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.00010824203491210938s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.62939453125e-06s
INFO | --- Analysis for iserve took 14.816271781921387s
Availability | SPARQL endpoint availability check for ISIC V4 took 22.110450983047485s
Availability | VoID file availability check for ISIC V4 took 0.0008599758148193359s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.31360650062561035s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.935264587402344e-05s
Believability | Calculation of trust value for ISIC V4 took 5.245208740234375e-06s
INFO | --- Analysis for isic-v4 took 117.51143765449524s
Availability | SPARQL endpoint availability check for Isidore took 4.5299530029296875e-05s
Availability | VoID file availability check for Isidore took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Isidore took 0.2680673599243164s
Reputation | Calculation of the PageRank for Isidore took 0.02100515365600586s
Interlinking | Calculation of Degree of Connection for Isidore took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Isidore took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.24249267578125e-05s
Believability | Calculation of trust value for Isidore took 9.059906005859375e-06s
INFO | --- Analysis for isidore took 3.5463485717773438s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.1961669921875e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2619459629058838s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 6.890296936035156e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 5.7220458984375e-06s
INFO | --- Analysis for isil-dbpedia took 4.836599826812744s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.076957702636719e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.3114814758300781s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.337860107421875e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 8.344650268554688e-06s
INFO | --- Analysis for iso-3166-2-data took 3.1184744834899902s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.3392181396484375e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.2783832550048828s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.600120544433594e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 6.9141387939453125e-06s
INFO | --- Analysis for iso-639-oasis took 3.142021656036377s
Availability | SPARQL endpoint availability check for ISOcat took 5.841255187988281e-05s
Availability | VoID file availability check for ISOcat took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for ISOcat took 0.2857685089111328s
Reputation | Calculation of the PageRank for ISOcat took 0.020801782608032227s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.127357482910156e-05s
Believability | Calculation of trust value for ISOcat took 7.62939453125e-06s
INFO | --- Analysis for isocat took 33.75649952888489s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.315376281738281e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.2841358184814453s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02090144157409668s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.647804260253906e-05s
Believability | Calculation of trust value for ISOcat-metadata took 9.298324584960938e-06s
INFO | --- Analysis for isocat-metadata took 5.083432674407959s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.076957702636719e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.28974008560180664s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.170967102050781e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 8.821487426757812e-06s
INFO | --- Analysis for ispra-lod-ihi took 3.0462646484375s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2671504020690918s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0003020763397216797s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.489897966384888s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7450094223022461s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20861029624938965s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.965573310852051s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 93.41809010505676s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16911721229553223s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12544488906860352s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17317986488342285s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1595451831817627s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1906578540802002s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2664060592651367s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.48028039932251s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1626131534576416s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.5229201316833496s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.551206111907959s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.23228144645690918s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22478866577148438s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15856003761291504s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.766072273254395s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.67572021484375e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24764776229858398s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28981876373291016s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5161356925964355s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5088036060333252s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2264997959136963s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.32080578804016113s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15725398063659668s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 15.407184839248657s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15736865997314453s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17807579040527344s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14817523956298828s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.972872257232666s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3057429790496826s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2611372470855713s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12972378730773926s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.813635110855103s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.0198252201080322s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.517809867858887s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1757237911224365s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.991506099700928s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2864990234375s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1363828182220459s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15381312370300293s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.712186574935913s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3518037796020508s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.1457672119140625e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-place took 512.553564786911s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.981590270996094e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.7373144626617432s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 2.86102294921875e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-rmn took 5.389436960220337s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.14519834518432617s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.000560760498046875s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 8.308834552764893s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.7803013324737549s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.254962682723999s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.938664674758911s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.45084023475647s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.2750434875488281s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.10179257392883301s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.20467209815979004s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.14026856422424316s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.15563464164733887s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.2588965892791748s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.71716523170471s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.17851948738098145s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.5031182765960693s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.5591323375701904s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.2437589168548584s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.21274089813232422s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.18541550636291504s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.65281891822815s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 0.00010275840759277344s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.250781774520874s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.25502657890319824s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4859130382537842s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.5157961845397949s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.238600492477417s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3362905979156494s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.1623241901397705s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 15.201850175857544s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.14890122413635254s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.13325214385986328s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.16202688217163086s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 4.652660608291626s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.30773258209228516s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2647116184234619s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.16258597373962402s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.700620174407959s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.93630051612854s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 4.203917503356934s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.1724283695220947s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.765066862106323s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.28509068489074707s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.19240760803222656s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.18022727966308594s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 4.643866777420044s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 1.2929973602294922s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.02077627182006836s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-ron took 464.4950385093689s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 3.933906555175781e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2873349189758301s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 2.8133392333984375e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 1.0013580322265625e-05s
INFO | --- Analysis for ispra-lod-sc took 3.0522148609161377s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 20.430768966674805s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2633037567138672s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.441375732421875e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 8.106231689453125e-06s
INFO | --- Analysis for issa-agritrop took 54.982242822647095s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.172325134277344e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.7182812690734863s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.8371810913085938e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.62939453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 4.697883367538452s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.100799560546875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2763357162475586s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.147125244140625e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.867813110351562e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 3.800368309020996s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.172325134277344e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.2834029197692871s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 2.9087066650390625e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 3.218650817871094e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 2.6766722202301025s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 2.0934677124023438s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.28421497344970703s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.630752563476562e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.4836273193359375e-06s
INFO | --- Analysis for istat-immigration took 4.596447944641113s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.076957702636719e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.3128981590270996s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 2.9325485229492188e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.867813110351562e-06s
INFO | --- Analysis for istat-immigrazione took 3.5203371047973633s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.24796819686889648s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2691919803619385s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.02016162872314453s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.9802322387695312e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 5.245208740234375e-06s
INFO | --- Analysis for it-aifa-drug-prices took 2.9982218742370605s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.5510199069976807s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2963685989379883s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0006973743438720703s
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 1.0251998901367188e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 4.140324115753174s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 6.580352783203125e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.2948434352874756s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 2.9087066650390625e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 8.106231689453125e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.997039794921875s
Availability | SPARQL endpoint availability check for Global Data on PFAS Contamination in Organisms took 4.076957702636719e-05s
Availability | VoID file availability check for Global Data on PFAS Contamination in Organisms took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Global Data on PFAS Contamination in Organisms took 0.2772946357727051s
Reputation | Calculation of the PageRank for Global Data on PFAS Contamination in Organisms took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Global Data on PFAS Contamination in Organisms took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Global Data on PFAS Contamination in Organisms took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Global Data on PFAS Contamination in Organisms took 1.3589859008789062e-05s
Believability | Calculation of trust value for Global Data on PFAS Contamination in Organisms took 8.58306884765625e-06s
INFO | --- Analysis for iue-PFASData took 2.4708192348480225s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 3.981590270996094e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.2597239017486572s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.075599670410156e-05s
Believability | Calculation of trust value for IWMI Research Reports took 1.2874603271484375e-05s
INFO | --- Analysis for iwmi-research-reports took 3.0739808082580566s
Availability | SPARQL endpoint availability check for IWN took 4.1484832763671875e-05s
Availability | VoID file availability check for IWN took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for IWN took 0.38182759284973145s
Reputation | Calculation of the PageRank for IWN took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for IWN took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IWN took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for IWN took 4.57763671875e-05s
Believability | Calculation of trust value for IWN took 8.106231689453125e-06s
INFO | --- Analysis for iwn took 363.2835600376129s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 3.933906555175781e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.7090556621551514s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.2901763916015625e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 8.344650268554688e-06s
INFO | --- Analysis for j-global-knowledge took 3.4552886486053467s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 3.910064697265625e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.2664945125579834s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.8848648071289062e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 7.3909759521484375e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 3.438261032104492s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.250621795654297s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0008189678192138672s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2884807586669922s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.127357482910156e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 7.867813110351562e-06s
INFO | --- Analysis for jamendo-dbtune took 24.810344219207764s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.076957702636719e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.27731847763061523s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.506111145019531e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for japan-radioactivity-stat took 5.316943168640137s
Availability | SPARQL endpoint availability check for JEL Classification took 4.1484832763671875e-05s
Availability | VoID file availability check for JEL Classification took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.26857733726501465s
Reputation | Calculation of the PageRank for JEL Classification took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for JEL Classification took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.8848648071289062e-05s
Believability | Calculation of trust value for JEL Classification took 6.67572021484375e-06s
INFO | --- Analysis for jel-classification took 4.894531011581421s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 0.33538365364074707s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.000579833984375s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.27170467376708984s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 2.9802322387695312e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.6450881958007812e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 6.934821128845215s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 262.35192584991455s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.6992990970611572s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020956993103027344s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.343292236328125e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 8.106231689453125e-06s
INFO | --- Analysis for jita took 541.1930270195007s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.1484832763671875e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.00030517578125s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.26653003692626953s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.0994415283203125e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.867813110351562e-06s
INFO | --- Analysis for jmdict took 3.7764885425567627s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.048973083496094s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.2616431713104248s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007076263427734375s
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.344650268554688e-06s
INFO | --- Analysis for john-goodwins-family-tree took 63.095348834991455s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.649162292480469e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2536954879760742s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.814697265625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 7.867813110351562e-06s
INFO | --- Analysis for jp-cos took 5.046408653259277s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.124641418457031e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.26574230194091797s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020747900009155273s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.00543212890625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 7.3909759521484375e-06s
INFO | --- Analysis for jp-textbook took 4.757763147354126s
Availability | SPARQL endpoint availability check for JRC-Names took 4.57763671875e-05s
Availability | VoID file availability check for JRC-Names took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.2509729862213135s
Reputation | Calculation of the PageRank for JRC-Names took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.552436828613281e-05s
Believability | Calculation of trust value for JRC-Names took 7.867813110351562e-06s
INFO | --- Analysis for jrc-names-ec took 4.715163946151733s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.8816797733306885s
Availability | VoID file availability check for JRC-Names-MLODE took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.2657337188720703s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.022866249084472656s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0011303424835205078s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 9.107589721679688e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 7.867813110351562e-06s
INFO | --- Analysis for jrc-names-mlode took 3.9191906452178955s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.267692565917969e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2657918930053711s
Reputation | Calculation of the PageRank for JudaicaLink took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010800361633300781s
Believability | Calculation of trust value for JudaicaLink took 7.62939453125e-06s
INFO | --- Analysis for judaicalink took 6.466318368911743s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 3.933906555175781e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.2675905227661133s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.2901763916015625e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 8.58306884765625e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.9684016704559326s
Availability | SPARQL endpoint availability check for KAKEN took 3.981590270996094e-05s
Availability | VoID file availability check for KAKEN took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for KAKEN took 0.2665140628814697s
Reputation | Calculation of the PageRank for KAKEN took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for KAKEN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for KAKEN took 2.956390380859375e-05s
Believability | Calculation of trust value for KAKEN took 7.3909759521484375e-06s
INFO | --- Analysis for kaken took 2.885509967803955s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07217669486999512s
Availability | VoID file availability check for Kallikratis municipalities took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.2821214199066162s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.393692016601562e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.245208740234375e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.5260729789733887s
Availability | SPARQL endpoint availability check for Openflights Routes took 5.1975250244140625e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.2758336067199707s
Reputation | Calculation of the PageRank for Openflights Routes took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.0279159545898438e-05s
Believability | Calculation of trust value for Openflights Routes took 5.9604644775390625e-06s
INFO | --- Analysis for kasabi-openflights-routes took 3.3773815631866455s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.38690185546875e-05s
Availability | VoID file availability check for EU Soccer League took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2638740539550781s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.075599670410156e-05s
Believability | Calculation of trust value for EU Soccer League took 7.152557373046875e-06s
INFO | --- Analysis for KG:Course_Submission took 3.6195621490478516s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.2438507080078125e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.2676570415496826s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1920928955078125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 7.867813110351562e-06s
INFO | --- Analysis for KING took 2.771758556365967s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.267692565917969e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2689707279205322s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.651878356933594e-05s
Believability | Calculation of trust value for Klappstuhlclub took 5.9604644775390625e-06s
INFO | --- Analysis for klappstuhlclub took 12.527217149734497s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.825160264968872s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.4465010166168213s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.02034473419189453s
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.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.508827209472656e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 6.67572021484375e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.434110641479492s
Availability | SPARQL endpoint availability check for Knowledge Forest took 3.910064697265625e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.24615478515625s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.9087066650390625e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.9141387939453125e-06s
INFO | --- Analysis for knowledge-map took 3.2964131832122803s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.220008850097656e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2856428623199463s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.7894973754882812e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.9141387939453125e-06s
INFO | --- Analysis for KnowledgeFusion took 2.38991641998291s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.363059997558594e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.24826955795288086s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020145416259765625s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.4849853515625e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.155964851379395s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.076957702636719e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.27152204513549805s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 2.956390380859375e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 8.58306884765625e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.8400137424468994s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.649162292480469e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.298170804977417s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.170967102050781e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.775161743164062e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.9763429164886475s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 8.96453857421875e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.2875325679779053s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.075599670410156e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 9.775161743164062e-06s
INFO | --- Analysis for ktr took 3.8482565879821777s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.1961669921875e-05s
Availability | VoID file availability check for Informatics Studies took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.6682863235473633s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.337860107421875e-05s
Believability | Calculation of trust value for Informatics Studies took 8.344650268554688e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 6.667506217956543s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 1.2190873622894287s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.22720623016357422s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 1.6661245822906494s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020114660263061523s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.4809112548828125e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 8.344650268554688e-06s
INFO | --- Analysis for kupkb took 9.92335033416748s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 5.841255187988281e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.3221166133880615s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020644187927246094s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007052421569824219s
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.867813110351562e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 8.1372389793396s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.238502502441406s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.5808472633361816s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020188093185424805s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 6.866455078125e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.867813110351562e-06s
INFO | --- Analysis for l3s-dblp took 50.89201998710632s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 25.162672758102417s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.8199582099914551s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.866455078125e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 8.821487426757812e-06s
INFO | --- Analysis for lak-dataset took 68.8734495639801s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.19972634315490723s
Availability | VoID file availability check for  Language Name Authority List  took 0.0007007122039794922s
Extra | Recovery of all triples for  Language Name Authority List  took 115.52272915840149s
Performance | Total latancy measurement for  Language Name Authority List  took 0.644416332244873s
Amount of data | Number of triples check for  Language Name Authority List  took 108.76705193519592s
Interoperability | New terms check for  Language Name Authority List  took 154.25562357902527s
Versatility | Languages check for  Language Name Authority List  took 300.0767340660095s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 8.553097248077393s
Security | Check HTTPS for  Language Name Authority List  took 0.30143213272094727s
Interpretability | RDF structures check for  Language Name Authority List  took 0.474240779876709s
Versatility | Serialization formats check for  Language Name Authority List  took 2.8880233764648438s
Availability | RDF dump link check for  Language Name Authority List  took 0.2126755714416504s
License | MR license check for  Language Name Authority List  took 0.21961688995361328s
License | HR license check for  Language Name Authority List  took 300.105429649353s
Amount of data | Number of property check for  Language Name Authority List  took 0.1692981719970703s
Understandability | Number of label check for  Language Name Authority List  took 7.198427438735962s
Understandability | URI regex check for  Language Name Authority List  took 0.2601003646850586s
Understandability | Vocabs check for  Language Name Authority List  took 0.11605334281921387s
Verifiability | Authors check for  Language Name Authority List  took 0.11646151542663574s
Verifiability | Publishers check for  Language Name Authority List  took 0.18293285369873047s
Performance | Throughput check for  Language Name Authority List  took 10.639370918273926s
Amount of data | Check the number of entities for  Language Name Authority List  took 0.00010848045349121094s
Verifiability | Contribs. check for  Language Name Authority List  took 0.19701719284057617s
Interlinking | sameAs chians check for  Language Name Authority List  took 11.034631729125977s
Interlinking | skos check for  Language Name Authority List  took 0.2646818161010742s
Interlinking | skos check for  Language Name Authority List  took 0.25449132919311523s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.18438482284545898s
Currency | Creation date check for  Language Name Authority List  took 0.3159677982330322s
Currency | Modification date check for  Language Name Authority List  took 0.1696007251739502s
Rep.Conc. | URIs length for  Language Name Authority List  took 518.151683807373s
Interoperability | New vocabularies check for  Language Name Authority List  took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.17619013786315918s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.17950201034545898s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.1454474925994873s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 27.189574241638184s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.1262924671173096s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.657792091369629s
Consistency | Disjoint class check for  Language Name Authority List  took 0.1715857982635498s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.46505427360535s
Consistency | Misplaced classes for  Language Name Authority List  took 8.519099473953247s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 38.24443030357361s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.4731125831604004s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.30355072021484s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 2.977972984313965s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.5010197162628174s
Security | Sign check for  Language Name Authority List  took 0.2134385108947754s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 4.130899429321289s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.2785604000091553s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021399497985839844s
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.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 2.1457672119140625e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.8358230590820312e-05s
INFO | --- Analysis for language-authority-list took 15589.672842741013s
Availability | SPARQL endpoint availability check for Lark took 385.83708119392395s
Availability | VoID file availability check for Lark took 0.0009949207305908203s
Completeness | Calculation of interlinking completeness for Lark took 0.9966402053833008s
Reputation | Calculation of the PageRank for Lark took 0.021304607391357422s
Interlinking | Calculation of Degree of Connection for Lark took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lark took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Lark took 0.00012731552124023438s
Believability | Calculation of trust value for Lark took 8.106231689453125e-06s
INFO | --- Analysis for LARK took 1555.438199520111s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.4149346351623535s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.25074005126953125s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.504753112792969e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 9.059906005859375e-06s
INFO | --- Analysis for LASLA took 4.923709392547607s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.100799560546875e-05s
Availability | VoID file availability check for LATC Linksets took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.2729771137237549s
Reputation | Calculation of the PageRank for LATC Linksets took 0.0204925537109375s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 2.9087066650390625e-05s
Believability | Calculation of trust value for LATC Linksets took 8.106231689453125e-06s
INFO | --- Analysis for latc-linksets took 3.8031086921691895s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.46089792251586914s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0008046627044677734s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.7430334091186523s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 5.359846591949463s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.4003880023956299s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.2895965576171875s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 5.245208740234375e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for LatinAffectus took 4.43561315536499s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.4700925350189209s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.7141716480255127s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.0201876163482666s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.810142278671265s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 3.8623809814453125e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.28159666061401367s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.62939453125e-06s
INFO | --- Analysis for lcc took 2.9737157821655273s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.100799560546875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2769172191619873s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011849403381347656s
Believability | Calculation of trust value for Library of Congress Subject Headings took 7.62939453125e-06s
INFO | --- Analysis for lcsh took 6.367873430252075s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 7.700920104980469e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.27265357971191406s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.106231689453125e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.867813110351562e-06s
INFO | --- Analysis for lcsubjects took 3.243708372116089s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.029273986816406e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.251589298248291s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.0203399658203125s
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.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 2.9325485229492188e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 6.9141387939453125e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.924403429031372s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 6.671516418457031s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.26636791229248047s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020147085189819336s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.100799560546875e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 8.344650268554688e-06s
INFO | --- Analysis for ldt@library took 31.428253650665283s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 5.793571472167969e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.282426118850708s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 2.9325485229492188e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 7.867813110351562e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.962805986404419s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 3.886222839355469e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.274324893951416s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.020561695098876953s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.2901763916015625e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 7.152557373046875e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.976299285888672s
Availability | SPARQL endpoint availability check for U ime Legije took 4.029273986816406e-05s
Availability | VoID file availability check for U ime Legije took 0.00021719932556152344s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.25825953483581543s
Reputation | Calculation of the PageRank for U ime Legije took 0.02070140838623047s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 2.956390380859375e-05s
Believability | Calculation of trust value for U ime Legije took 7.3909759521484375e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.362912178039551s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.029273986816406e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.29895496368408203s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.021545886993408203s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.218650817871094e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 8.344650268554688e-06s
INFO | --- Analysis for legislation-openuplabs took 3.4341280460357666s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.43268918991088867s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.25725388526916504s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.104873657226562e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 8.58306884765625e-06s
INFO | --- Analysis for LemmaBank took 4.484898328781128s
Availability | SPARQL endpoint availability check for lemonUby took 4.172325134277344e-05s
Availability | VoID file availability check for lemonUby took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for lemonUby took 0.26178717613220215s
Reputation | Calculation of the PageRank for lemonUby took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for lemonUby took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.318092346191406e-05s
Believability | Calculation of trust value for lemonUby took 7.152557373046875e-06s
INFO | --- Analysis for lemonuby took 3.169044256210327s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.1484832763671875e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.2539961338043213s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 4.3392181396484375e-05s
Believability | Calculation of trust value for LemonWiktionary took 6.9141387939453125e-06s
INFO | --- Analysis for lemonwiktionary took 4.152203559875488s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.4236729145050049s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.2845306396484375s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 8.344650268554688e-06s
INFO | --- Analysis for LewisShort took 4.210726022720337s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.0879909992218018s
Availability | VoID file availability check for LEXIN-RDF took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.26166749000549316s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for LEXIN-RDF took 7.867813110351562e-06s
INFO | --- Analysis for lexin-rdf took 5.560533046722412s
Availability | SPARQL endpoint availability check for lexinfo took 4.1961669921875e-05s
Availability | VoID file availability check for lexinfo took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for lexinfo took 0.24694442749023438s
Reputation | Calculation of the PageRank for lexinfo took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.845329284667969e-05s
Believability | Calculation of trust value for lexinfo took 7.62939453125e-06s
INFO | --- Analysis for lexinfo took 2.8346195220947266s
Availability | SPARQL endpoint availability check for Lexvo took 4.1961669921875e-05s
Availability | VoID file availability check for Lexvo took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Lexvo took 0.24557876586914062s
Reputation | Calculation of the PageRank for Lexvo took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017261505126953125s
Believability | Calculation of trust value for Lexvo took 7.867813110351562e-06s
INFO | --- Analysis for lexvo took 3.218026876449585s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.291534423828125e-05s
Availability | VoID file availability check for Lexvo.org took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.2804713249206543s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.367134094238281e-05s
Believability | Calculation of trust value for Lexvo.org took 7.3909759521484375e-06s
INFO | --- Analysis for lexvo-org took 2.601158380508423s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3042104244232178s
Availability | VoID file availability check for LIBRIS took 0.0006189346313476562s
Extra | Recovery of all triples for LIBRIS took 18.082671403884888s
Performance | Total latancy measurement for LIBRIS took 0.7130062580108643s
Amount of data | Number of triples check for LIBRIS took 24.956188440322876s
Interoperability | New terms check for LIBRIS took 16.459919452667236s
Versatility | Languages check for LIBRIS took 0.18834519386291504s
Interpretability | Number of blank nodes check for LIBRIS took 300.0876133441925s
Security | Check HTTPS for LIBRIS took 0.3491332530975342s
Interpretability | RDF structures check for LIBRIS took 0.21398615837097168s
Versatility | Serialization formats check for LIBRIS took 0.19152045249938965s
Availability | RDF dump link check for LIBRIS took 0.12860870361328125s
License | MR license check for LIBRIS took 0.15670156478881836s
License | HR license check for LIBRIS took 0.15469670295715332s
Amount of data | Number of property check for LIBRIS took 0.18392109870910645s
Understandability | Number of label check for LIBRIS took 0.25792360305786133s
Understandability | URI regex check for LIBRIS took 0.30195188522338867s
Understandability | Vocabs check for LIBRIS took 0.14350128173828125s
Verifiability | Authors check for LIBRIS took 0.13748788833618164s
Verifiability | Publishers check for LIBRIS took 0.1287832260131836s
Performance | Throughput check for LIBRIS took 10.58304738998413s
Amount of data | Check the number of entities for LIBRIS took 0.00011301040649414062s
Verifiability | Contribs. check for LIBRIS took 0.14549779891967773s
Interlinking | sameAs chians check for LIBRIS took 0.16115593910217285s
Interlinking | skos check for LIBRIS took 0.14702081680297852s
Interlinking | skos check for LIBRIS took 0.12930035591125488s
Timeliness | dataset update frequency check for LIBRIS took 0.13127779960632324s
Currency | Creation date check for LIBRIS took 0.32881665229797363s
Currency | Modification date check for LIBRIS took 0.598637580871582s
Rep.Conc. | URIs length for LIBRIS took 85.6386079788208s
Interoperability | New vocabularies check for LIBRIS took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.18102526664733887s
Accuracy | Check Functional Property for LIBRIS took 0.1748335361480713s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.12921547889709473s
Accuracy | Check Datatype consistency for LIBRIS took 0.267378568649292s
Consistency | Disjoint class check for LIBRIS took 0.17308831214904785s
Consistency | Check Misplaced properties for LIBRIS took 62.93623614311218s
Consistency | Misplaced classes for LIBRIS took 1.101705551147461s
Consistency | Check Ontology hijacking for LIBRIS took 6.460181951522827s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1590948104858398s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 63.789512157440186s
Conciseness | Check Extensional conciseness for LIBRIS took 0.27779507637023926s
Conciseness | Check Intensional conciseness for LIBRIS took 0.41368794441223145s
Security | Sign check for LIBRIS took 0.1481771469116211s
Availability | Check URIs Dereferenciability for LIBRIS took 5.475640773773193s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.2244460582733154s
Reputation | Calculation of the PageRank for LIBRIS took 0.0200958251953125s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.6689300537109375e-06s
Believability | Calculation of trust value for LIBRIS took 8.106231689453125e-06s
INFO | --- Analysis for libris took 1093.5126719474792s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.19443202018737793s
Availability | VoID file availability check for Public Library of Veroia took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.7230865955352783s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.486343383789062e-05s
Believability | Calculation of trust value for Public Library of Veroia took 9.059906005859375e-06s
INFO | --- Analysis for libver took 5.919754505157471s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.20527029037475586s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.2651553153991699s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.130073547363281e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.9604644775390625e-06s
INFO | --- Analysis for lichfield-spending took 3.481574535369873s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.4345855712890625e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007052421569824219s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.27583885192871094s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.600120544433594e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 7.152557373046875e-06s
INFO | --- Analysis for lime took 8.511977672576904s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.172325134277344e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.2778937816619873s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010323524475097656s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.867813110351562e-06s
INFO | --- Analysis for lingvoj took 6.272703647613525s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 7.939338684082031e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.26851797103881836s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.273124694824219e-05s
Believability | Calculation of trust value for Linked Crunchbase took 7.62939453125e-06s
INFO | --- Analysis for linked-crunchbase took 2.828659772872925s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.265510082244873s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.26890087127685547s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0009756088256835938s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.392333984375e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.58306884765625e-06s
INFO | --- Analysis for linked-drugs took 19.630911111831665s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.9114227294921875e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2680788040161133s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.00010013580322265625s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 6.67572021484375e-06s
INFO | --- Analysis for linked-edgar took 4.0159220695495605s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0003268718719482422s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.25493574142456055s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.608268737792969e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.152557373046875e-06s
INFO | --- Analysis for linked-eurostat took 3.374577045440674s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.124641418457031e-05s
Availability | VoID file availability check for linked hypernyms took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2784304618835449s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.176399230957031e-05s
Believability | Calculation of trust value for linked hypernyms took 5.7220458984375e-06s
INFO | --- Analysis for linked-hypernyms took 3.3274614810943604s
Availability | SPARQL endpoint availability check for Linked Life Data took 226.80755138397217s
Availability | VoID file availability check for Linked Life Data took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Linked Life Data took 1.071284294128418s
Reputation | Calculation of the PageRank for Linked Life Data took 0.02073836326599121s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.553794860839844e-05s
Believability | Calculation of trust value for Linked Life Data took 7.867813110351562e-06s
INFO | --- Analysis for linked-life-data took 692.0575563907623s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.2743980884552002s
Availability | VoID file availability check for Linked Logainm took 0.000499725341796875s
Extra | Recovery of all triples for Linked Logainm took 2.7361226081848145s
Performance | Total latancy measurement for Linked Logainm took 0.5789656639099121s
Amount of data | Number of triples check for Linked Logainm took 0.18453526496887207s
Interoperability | New terms check for Linked Logainm took 1.3363332748413086s
Versatility | Languages check for Linked Logainm took 1.5392510890960693s
Interpretability | Number of blank nodes check for Linked Logainm took 0.1434955596923828s
Security | Check HTTPS for Linked Logainm took 0.27564120292663574s
Interpretability | RDF structures check for Linked Logainm took 0.26897287368774414s
Versatility | Serialization formats check for Linked Logainm took 0.14912676811218262s
Availability | RDF dump link check for Linked Logainm took 0.11536407470703125s
License | MR license check for Linked Logainm took 0.1330873966217041s
License | HR license check for Linked Logainm took 0.11904311180114746s
Amount of data | Number of property check for Linked Logainm took 0.14855504035949707s
Understandability | Number of label check for Linked Logainm took 0.22214174270629883s
Understandability | URI regex check for Linked Logainm took 0.24607253074645996s
Understandability | Vocabs check for Linked Logainm took 0.11643600463867188s
Verifiability | Authors check for Linked Logainm took 0.12233257293701172s
Verifiability | Publishers check for Linked Logainm took 0.1065676212310791s
Performance | Throughput check for Linked Logainm took 10.67090892791748s
Amount of data | Check the number of entities for Linked Logainm took 0.00010538101196289062s
Verifiability | Contribs. check for Linked Logainm took 0.11760234832763672s
Interlinking | sameAs chians check for Linked Logainm took 0.14855575561523438s
Interlinking | skos check for Linked Logainm took 0.14955925941467285s
Interlinking | skos check for Linked Logainm took 0.11137199401855469s
Timeliness | dataset update frequency check for Linked Logainm took 0.11635804176330566s
Currency | Creation date check for Linked Logainm took 0.2613558769226074s
Currency | Modification date check for Linked Logainm took 0.2593269348144531s
Rep.Conc. | URIs length for Linked Logainm took 1.0049653053283691s
Interoperability | New vocabularies check for Linked Logainm took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.14963388442993164s
Accuracy | Check Functional Property for Linked Logainm took 0.22101426124572754s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.20897150039672852s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.6430442333221436s
Accuracy | Check White space in annotation for Linked Logainm took 0.024050235748291016s
Accuracy | Check Datatype consistency for Linked Logainm took 0.02798938751220703s
Consistency | Disjoint class check for Linked Logainm took 0.18830609321594238s
Consistency | Check Misplaced properties for Linked Logainm took 0.35297632217407227s
Consistency | Misplaced classes for Linked Logainm took 0.28533482551574707s
Consistency | Check Ontology hijacking for Linked Logainm took 1.8328678607940674s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.172811508178711s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.40663480758667s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.0355377197265625s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.20371007919311523s
Security | Sign check for Linked Logainm took 0.11888480186462402s
Availability | Check URIs Dereferenciability for Linked Logainm took 982.225291967392s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.8523151874542236s
Reputation | Calculation of the PageRank for Linked Logainm took 0.0251920223236084s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 0.00018787384033203125s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Logainm took 8.344650268554688e-06s
INFO | --- Analysis for linked-logainm took 1040.5378558635712s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.38690185546875e-05s
Availability | VoID file availability check for Linked NUTS took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.7213656902313232s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.1021575927734375e-05s
Believability | Calculation of trust value for Linked NUTS took 5.4836273193359375e-06s
INFO | --- Analysis for linked-nuts took 4.644673824310303s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 3.8623809814453125e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.7659022808074951s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020268678665161133s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.86102294921875e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 7.867813110351562e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 5.718372344970703s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.8046274185180664s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2717714309692383s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.9604644775390625e-06s
INFO | --- Analysis for linked-open-camera took 5.2965247631073s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.4601335525512695s
Availability | VoID file availability check for Linked Open Commerce took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2651219367980957s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 2.765655517578125e-05s
Believability | Calculation of trust value for Linked Open Commerce took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-commerce took 11.346714735031128s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.5582308769226074s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.2844817638397217s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020458221435546875s
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.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00011920928955078125s
Believability | Calculation of trust value for Linked Open Data of Ecology took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 4.513636589050293s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2628958225250244s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.608268737792969e-05s
Believability | Calculation of trust value for Linked Open Numbers took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-numbers took 2.6967976093292236s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 7.319450378417969e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2705812454223633s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked Open Piracy took 6.198883056640625e-06s
INFO | --- Analysis for linked-open-piracy took 6.150400161743164s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 3.9577484130859375e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.30872154235839844s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-senate took 2.978351354598999s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.0941534042358398s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.2866063117980957s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.02127861976623535s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.887580871582031e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 6.245377779006958s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2706019878387451s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020231962203979492s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.7220458984375e-06s
INFO | --- Analysis for linked-periodicals took 2.591480016708374s
Availability | SPARQL endpoint availability check for Linked Index took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Index took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Linked Index took 0.26895689964294434s
Reputation | Calculation of the PageRank for Linked Index took 0.02025127410888672s
Interlinking | Calculation of Degree of Connection for Linked Index took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Linked Index took 7.772445678710938e-05s
Believability | Calculation of trust value for Linked Index took 7.152557373046875e-06s
INFO | --- Analysis for linked-stockindex took 2.4654734134674072s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.928469181060791s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2761843204498291s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.03280997276306152s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.001416921615600586s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 6.437301635742188e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 8.58306884765625e-06s
INFO | --- Analysis for linked-structured-product-labels took 32.743486166000366s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.9476165771484375s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2604658603668213s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.4332275390625e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 8.106231689453125e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 4.2845540046691895s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.19350028038025s
Availability | VoID file availability check for Linked TCGA took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.262955904006958s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked TCGA took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.273124694824219e-05s
Believability | Calculation of trust value for Linked TCGA took 1.3828277587890625e-05s
INFO | --- Analysis for linked-tcga took 63.088709354400635s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.2213428020477295s
Availability | VoID file availability check for Linked User Feedback took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.2719454765319824s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.838539123535156e-05s
Believability | Calculation of trust value for Linked User Feedback took 7.152557373046875e-06s
INFO | --- Analysis for linked-user-feedback took 3.024035692214966s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.124641418457031e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2518134117126465s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.581710815429688e-05s
Believability | Calculation of trust value for USPTO Patent data took 6.4373016357421875e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.062453746795654s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 3.933906555175781e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.26447510719299316s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 6.9141387939453125e-06s
INFO | --- Analysis for linked-web-apis took 2.910231113433838s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.172325134277344e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2986423969268799s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 2.9087066650390625e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 7.867813110351562e-06s
INFO | --- Analysis for linkedarc took 3.537337064743042s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.08053135871887207s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.26708221435546875s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.0517578125e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 7.3909759521484375e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.7181379795074463s
Availability | SPARQL endpoint availability check for LinkedCT took 1.508666753768921s
Availability | VoID file availability check for LinkedCT took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.2640814781188965s
Reputation | Calculation of the PageRank for LinkedCT took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for LinkedCT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.274482727050781e-05s
Believability | Calculation of trust value for LinkedCT took 7.62939453125e-06s
INFO | --- Analysis for linkedct took 5.265218734741211s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.2272331714630127s
Availability | VoID file availability check for LinkedGeoData took 0.0004837512969970703s
Extra | Recovery of all triples for LinkedGeoData took 14.77899980545044s
Performance | Total latancy measurement for LinkedGeoData took 0.7026596069335938s
Amount of data | Number of triples check for LinkedGeoData took 47.29517483711243s
Interoperability | New terms check for LinkedGeoData took 90.69840860366821s
Versatility | Languages check for LinkedGeoData took 180.64429354667664s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.22638630867004395s
Security | Check HTTPS for LinkedGeoData took 0.33117055892944336s
Interpretability | RDF structures check for LinkedGeoData took 0.7809615135192871s
Versatility | Serialization formats check for LinkedGeoData took 0.33290839195251465s
Availability | RDF dump link check for LinkedGeoData took 0.15079760551452637s
License | MR license check for LinkedGeoData took 0.5825304985046387s
License | HR license check for LinkedGeoData took 86.53184151649475s
Amount of data | Number of property check for LinkedGeoData took 0.31529974937438965s
Understandability | Number of label check for LinkedGeoData took 2.004521131515503s
Understandability | URI regex check for LinkedGeoData took 0.3867037296295166s
Understandability | Vocabs check for LinkedGeoData took 0.17229199409484863s
Verifiability | Authors check for LinkedGeoData took 0.15667963027954102s
Verifiability | Publishers check for LinkedGeoData took 0.12422847747802734s
Performance | Throughput check for LinkedGeoData took 10.681116342544556s
Amount of data | Check the number of entities for LinkedGeoData took 0.06209564208984375s
Verifiability | Contribs. check for LinkedGeoData took 2.1002910137176514s
Interlinking | sameAs chians check for LinkedGeoData took 0.3061497211456299s
Interlinking | skos check for LinkedGeoData took 0.4031679630279541s
Interlinking | skos check for LinkedGeoData took 0.1314685344696045s
Timeliness | dataset update frequency check for LinkedGeoData took 0.35930442810058594s
Currency | Creation date check for LinkedGeoData took 0.4837174415588379s
Currency | Modification date check for LinkedGeoData took 2.4176604747772217s
Rep.Conc. | URIs length for LinkedGeoData took 272.588458776474s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.1775374412536621s
Accuracy | Check Functional Property for LinkedGeoData took 0.21325135231018066s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.18101859092712402s
Accuracy | Check Empty annotation labels for LinkedGeoData took 2.9020626544952393s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15717220306396484s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13423967361450195s
Consistency | Disjoint class check for LinkedGeoData took 0.2132411003112793s
Consistency | Check Misplaced properties for LinkedGeoData took 182.0925576686859s
Consistency | Misplaced classes for LinkedGeoData took 0.6531980037689209s
Consistency | Check Ontology hijacking for LinkedGeoData took 4.7579734325408936s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.1963183879852295s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.8117835521698s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.1524794101715088s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.318467378616333s
Security | Sign check for LinkedGeoData took 0.7005128860473633s
Availability | Check URIs Dereferenciability for LinkedGeoData took 6.14574933052063s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 1.421818494796753s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021763324737548828s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00012731552124023438s
Believability | Calculation of trust value for LinkedGeoData took 9.5367431640625e-06s
INFO | --- Analysis for linkedgeodata took 2157.171414375305s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.1484832763671875e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.27281689643859863s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.0221102237701416s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.1948089599609375e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 8.106231689453125e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 5.113035440444946s
Availability | SPARQL endpoint availability check for LinkedLCCN took 0.7904109954833984s
Availability | VoID file availability check for LinkedLCCN took 0.0008234977722167969s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.3553502559661865s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010013580322265625s
Believability | Calculation of trust value for LinkedLCCN took 7.62939453125e-06s
INFO | --- Analysis for linkedlccn took 17.269798755645752s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.100799560546875e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2602052688598633s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.3855438232421875e-05s
Believability | Calculation of trust value for LinkedMarkMail took 7.62939453125e-06s
INFO | --- Analysis for linkedmarkmail took 3.052090883255005s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.62308096885681s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007574558258056641s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2887742519378662s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013184547424316406s
Believability | Calculation of trust value for Linked Movie DataBase took 8.106231689453125e-06s
INFO | --- Analysis for linkedmdb took 134.73718428611755s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.47038960456848145s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.6884052753448486s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02014780044555664s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 6.985664367675781e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for linkedspending took 5.421277284622192s
Availability | SPARQL endpoint availability check for LinkedStats took 4.0531158447265625e-05s
Availability | VoID file availability check for LinkedStats took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2825191020965576s
Reputation | Calculation of the PageRank for LinkedStats took 0.021143198013305664s
Interlinking | Calculation of Degree of Connection for LinkedStats took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.0040740966796875e-05s
Believability | Calculation of trust value for LinkedStats took 7.867813110351562e-06s
INFO | --- Analysis for linkedstats took 4.698993444442749s
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.0002474784851074219s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.2768545150756836s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 2.9087066650390625e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.922762870788574s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.0531158447265625e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.7171347141265869s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 6.9141387939453125e-06s
INFO | --- Analysis for linking-open-drug-data took 3.4140117168426514s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.057878971099853516s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.24797558784484863s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02065443992614746s
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.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010704994201660156s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 7.3909759521484375e-06s
INFO | --- Analysis for linklion took 2.4395358562469482s
Availability | SPARQL endpoint availability check for Lion's Den took 3.9577484130859375e-05s
Availability | VoID file availability check for Lion's Den took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.7218549251556396s
Reputation | Calculation of the PageRank for Lion's Den took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for Lion's Den took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 2.9087066650390625e-05s
Believability | Calculation of trust value for Lion's Den took 7.62939453125e-06s
INFO | --- Analysis for lionsden took 3.917111873626709s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 35.9861319065094s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.27523207664489746s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020320415496826172s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.054473876953125e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 6.4373016357421875e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 41.364357709884644s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.029273986816406e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.28823018074035645s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.02044677734375s
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.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 8.821487426757812e-06s
INFO | --- Analysis for livtdm took 2.9375460147857666s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 3.9577484130859375e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.28755640983581543s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.86102294921875e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 1.0251998901367188e-05s
INFO | --- Analysis for livtdm2017 took 2.976590156555176s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.25862765312194824s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 3.170967102050781e-05s
INFO | --- Analysis for lobi took 2.9083642959594727s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.1405308246612549s
Availability | VoID file availability check for lobid-organisations took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.2920846939086914s
Reputation | Calculation of the PageRank for lobid-organisations took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.369850158691406e-05s
Believability | Calculation of trust value for lobid-organisations took 8.821487426757812e-06s
INFO | --- Analysis for lobid-organisations took 6.133878469467163s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.866814136505127s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.2692687511444092s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.751319885253906e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 8.106231689453125e-06s
INFO | --- Analysis for lobid-resources took 8.072360754013062s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2739143371582031s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.024622440338134766s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0012462139129638672s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 9.584426879882812e-05s
Believability | Calculation of trust value for Linked Open Colors took 8.106231689453125e-06s
INFO | --- Analysis for loc took 8.749548196792603s
Availability | SPARQL endpoint availability check for Location Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Location Ontology took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.24830245971679688s
Reputation | Calculation of the PageRank for Location Ontology took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for Location Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Location Ontology took 4.315376281738281e-05s
INFO | --- Analysis for Location_Ontology took 3.730181932449341s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 5.793571472167969e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.9308526515960693s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 9.775161743164062e-06s
INFO | --- Analysis for locv took 36.9245445728302s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.75887131690979s
Availability | VoID file availability check for LOD-a-lot took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.7040088176727295s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.9325485229492188e-05s
Believability | Calculation of trust value for LOD-a-lot took 8.344650268554688e-06s
INFO | --- Analysis for lod-a-lot took 14.367010354995728s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.0531158447265625e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.3090474605560303s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.314018249511719e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 8.58306884765625e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 3.8324475288391113s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.458427429199219e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.26720142364501953s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.0279159545898438e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 9.059906005859375e-06s
INFO | --- Analysis for lod-taiwan took 2.958949327468872s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.1961669921875e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2692131996154785s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.7738037109375e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 7.867813110351562e-06s
INFO | --- Analysis for lod2-project-wiki took 3.6594972610473633s
Availability | SPARQL endpoint availability check for LODAC BDLS took 3.3086812496185303s
Availability | VoID file availability check for LODAC BDLS took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2733938694000244s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.963180541992188e-05s
Believability | Calculation of trust value for LODAC BDLS took 7.152557373046875e-06s
INFO | --- Analysis for lodac-bdls took 14.335294485092163s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.291534423828125e-05s
Availability | VoID file availability check for LODRussia Math took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2757737636566162s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020917415618896484s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 3.075599670410156e-05s
Believability | Calculation of trust value for LODRussia Math took 6.67572021484375e-06s
INFO | --- Analysis for lodrussia-math took 2.9760866165161133s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.029273986816406e-05s
Availability | VoID file availability check for LODRussia Nano took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.2723979949951172s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.170967102050781e-05s
Believability | Calculation of trust value for LODRussia Nano took 7.867813110351562e-06s
INFO | --- Analysis for lodrussia-nano took 2.926114320755005s
Availability | SPARQL endpoint availability check for LODStats took 4.076957702636719e-05s
Availability | VoID file availability check for LODStats took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for LODStats took 0.27674102783203125s
Reputation | Calculation of the PageRank for LODStats took 0.0245819091796875s
Interlinking | Calculation of Degree of Connection for LODStats took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for LODStats took 0.001249074935913086s
Interlinking | Calculation of Clustering coefficient for LODStats took 4.506111145019531e-05s
Believability | Calculation of trust value for LODStats took 8.106231689453125e-06s
INFO | --- Analysis for lodstats took 2.9801218509674072s
Availability | SPARQL endpoint availability check for LODUM took 3.933906555175781e-05s
Availability | VoID file availability check for LODUM took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for LODUM took 0.2710754871368408s
Reputation | Calculation of the PageRank for LODUM took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for LODUM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.9087066650390625e-05s
Believability | Calculation of trust value for LODUM took 8.344650268554688e-06s
INFO | --- Analysis for lodum took 2.852400064468384s
Availability | SPARQL endpoint availability check for lofd took 0.1295146942138672s
Availability | VoID file availability check for lofd took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for lofd took 0.2529561519622803s
Reputation | Calculation of the PageRank for lofd took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for lofd took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lofd took 0.0006999969482421875s
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.5588903427124023s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.76917481422424s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007548332214355469s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2700345516204834s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 6.198883056640625e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 5.7220458984375e-06s
INFO | --- Analysis for loius took 587.9008693695068s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.2438507080078125e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.26129817962646484s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 3.0279159545898438e-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.219256639480591s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 1.7137930393218994s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.3076653480529785s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.1021575927734375e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.245208740234375e-06s
INFO | --- Analysis for london-gazette took 8.327681064605713s
Availability | SPARQL endpoint availability check for Weather Stations took 4.220008850097656e-05s
Availability | VoID file availability check for Weather Stations took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.25603580474853516s
Reputation | Calculation of the PageRank for Weather Stations took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for Weather Stations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 9.846687316894531e-05s
Believability | Calculation of trust value for Weather Stations took 7.3909759521484375e-06s
INFO | --- Analysis for los_metar took 4.684369087219238s
Availability | SPARQL endpoint availability check for Lotico took 0.9114305973052979s
Availability | VoID file availability check for Lotico took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Lotico took 0.2719862461090088s
Reputation | Calculation of the PageRank for Lotico took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Lotico took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lotico took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Lotico took 7.963180541992188e-05s
Believability | Calculation of trust value for Lotico took 7.152557373046875e-06s
INFO | --- Analysis for lotico took 7.61062216758728s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.4686851501464844s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.2635679244995117s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.457069396972656e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 8.821487426757812e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 4.610837459564209s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5919373035430908s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00027680397033691406s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 119.93976140022278s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9331879615783691s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.374186515808105s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 17.915062427520752s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2484941482544s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7568373680114746s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.26367616653442383s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.691444873809814s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.28182363510131836s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.541914701461792s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.17620038986206s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5482065677642822s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.4492976665496826s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6445002555847168s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.32219386100769043s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19777297973632812s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.27904224395751953s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.190404415130615s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.082389831542969e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20499420166015625s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19446086883544922s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.46340465545654297s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.48166418075561523s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.237108945846558s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4683074951171875s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2305741310119629s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 175.17056369781494s
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.19648528099060059s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22054696083068848s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24748468399047852s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 47.81800985336304s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6669673919677734s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6637535095214844s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19786953926086426s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 91.1785683631897s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.485397100448608s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 35.83081841468811s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2139716148376465s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 90.39690113067627s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.777195930480957s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.581712007522583s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.7084038257598877s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.102190256118774s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.4546849727630615s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.022395610809326172s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.1961669921875e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.821487426757812e-06s
INFO | --- Analysis for LPIS_(Poland) took 2280.8556368350983s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2059793472290039s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.00026535987854003906s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 120.70671486854553s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9128072261810303s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.90519094467163s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 15.187435150146484s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.15404772758484s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.4823880195617676s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21978044509887695s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.196037292480469s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.25237464904785156s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3769032955169678s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.1668870449066s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.29941582679748535s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.655548334121704s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.7531130313873291s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3785381317138672s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20483660697937012s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.27617430686950684s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.2905912399292s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.749961853027344e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21310710906982422s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19710159301757812s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4581887722015381s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.583071231842041s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.721911191940308s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5002548694610596s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2175304889678955s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 153.10245966911316s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.195387601852417s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3322463035583496s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.33484792709350586s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.04513740539551s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.667668342590332s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.703395128250122s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19182610511779785s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 93.3683557510376s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.525630474090576s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 37.16663336753845s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.261582612991333s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 89.64608263969421s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7805323600769043s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.582554817199707s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.7776496410369873s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 18.577794551849365s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1592838764190674s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 2292.4243862628937s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.172325134277344e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0009195804595947266s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.7801845073699951s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.027453184127807617s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 2.7179718017578125e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0013494491577148438s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 6.365776062011719e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 7.62939453125e-06s
INFO | --- Analysis for lremap-auth took 487.1171009540558s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.315376281738281e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.7204995155334473s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02068305015563965s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.6716461181640625e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 7.3909759521484375e-06s
INFO | --- Analysis for lremap-conf took 245.70094347000122s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.172325134277344e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.8458030223846436s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.021062135696411133s
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.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 4.172325134277344e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 7.62939453125e-06s
INFO | --- Analysis for lremap-ri took 244.92564415931702s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.410743713378906e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.37546396255493164s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.02094554901123047s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 4.124641418457031e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 7.62939453125e-06s
INFO | --- Analysis for lremap-sub took 244.77790760993958s
Availability | SPARQL endpoint availability check for LSQ took 4.124641418457031e-05s
Availability | VoID file availability check for LSQ took 0.000335693359375s
Completeness | Calculation of interlinking completeness for LSQ took 0.2728912830352783s
Reputation | Calculation of the PageRank for LSQ took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for LSQ took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LSQ took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.7894973754882812e-05s
Believability | Calculation of trust value for LSQ took 7.62939453125e-06s
INFO | --- Analysis for lsq took 4.831820249557495s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.588362455368042s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2953355312347412s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 8.821487426757812e-06s
INFO | --- Analysis for LucaniPharsalia took 5.421397924423218s
Availability | SPARQL endpoint availability check for Linked rules took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked rules took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2744002342224121s
Reputation | Calculation of the PageRank for Linked rules took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for Linked rules took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked rules took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Linked rules took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked rules took 7.62939453125e-06s
INFO | --- Analysis for Luminaires_senlis took 2.3968803882598877s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.4345855712890625e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0003826618194580078s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.2766225337982178s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.0279159545898438e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 8.58306884765625e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 3.427924156188965s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.233728647232056s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.2571582794189453s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 2.8371810913085938e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for makg took 63.671566009521484s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.220008850097656e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.00033020973205566406s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.26018691062927246s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.3855438232421875e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.239776611328125e-05s
INFO | --- Analysis for manchester-university-reading-lists took 4.420419454574585s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.315376281738281e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.27186012268066406s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.3855438232421875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.867813110351562e-06s
INFO | --- Analysis for manish took 2.3695969581604004s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.100799560546875e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.2657802104949951s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 3.0517578125e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 8.58306884765625e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.8464608192443848s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.029273986816406e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.2856171131134033s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.075599670410156e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 7.152557373046875e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 3.0050835609436035s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.267692565917969e-05s
Availability | VoID file availability check for MARC Codes List took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2675344944000244s
Reputation | Calculation of the PageRank for MARC Codes List took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012993812561035156s
Believability | Calculation of trust value for MARC Codes List took 8.344650268554688e-06s
INFO | --- Analysis for marc-codes took 15.092512845993042s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.28226327896118164s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02073836326599121s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.981590270996094e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 7.152557373046875e-06s
INFO | --- Analysis for masc took 6.161219120025635s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.076957702636719e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2591574192047119s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.814697265625e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 8.58306884765625e-06s
INFO | --- Analysis for masc-bn-nif took 5.860440015792847s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.6499671936035156s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2586081027984619s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.8848648071289062e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 6.9141387939453125e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.243385314941406s
Availability | SPARQL endpoint availability check for medline took 5.4836273193359375e-05s
Availability | VoID file availability check for medline took 0.00034546852111816406s
Completeness | Calculation of interlinking completeness for medline took 0.2561485767364502s
Reputation | Calculation of the PageRank for medline took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for medline took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for medline took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for medline took 3.3855438232421875e-05s
Believability | Calculation of trust value for medline took 8.106231689453125e-06s
INFO | --- Analysis for medline took 8.751233339309692s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 2.0736899375915527s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2759876251220703s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.580352783203125e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 8.106231689453125e-06s
INFO | --- Analysis for meducator took 16.474422454833984s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 3.9577484130859375e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2568545341491699s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020100831985473633s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.8371810913085938e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 7.62939453125e-06s
INFO | --- Analysis for mesh-finnish took 2.9122560024261475s
Availability | SPARQL endpoint availability check for MeSH headings took 4.029273986816406e-05s
Availability | VoID file availability check for MeSH headings took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.2587740421295166s
Reputation | Calculation of the PageRank for MeSH headings took 0.020364999771118164s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.9087066650390625e-05s
Believability | Calculation of trust value for MeSH headings took 3.838539123535156e-05s
INFO | --- Analysis for mesh_headings took 2.936511993408203s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.8160552978515625e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2967073917388916s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.021255016326904297s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 2.9087066650390625e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 3.361701965332031e-05s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.942312479019165s
Availability | SPARQL endpoint availability check for MeSH pairs took 3.910064697265625e-05s
Availability | VoID file availability check for MeSH pairs took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2623465061187744s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.7894973754882812e-05s
Believability | Calculation of trust value for MeSH pairs took 6.67572021484375e-06s
INFO | --- Analysis for mesh_pairs took 2.9554636478424072s
Availability | SPARQL endpoint availability check for MeSH titles took 3.981590270996094e-05s
Availability | VoID file availability check for MeSH titles took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.2622032165527344s
Reputation | Calculation of the PageRank for MeSH titles took 0.02007889747619629s
Interlinking | Calculation of Degree of Connection for MeSH titles took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 2.8848648071289062e-05s
Believability | Calculation of trust value for MeSH titles took 7.3909759521484375e-06s
INFO | --- Analysis for mesh_titles took 2.8578343391418457s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.410743713378906e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.27085280418395996s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.337860107421875e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 1.1444091796875e-05s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.8841662406921387s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.363059997558594e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.27255868911743164s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.170967102050781e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.106231689453125e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.89772629737854s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.291534423828125e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.26404404640197754s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.271766662597656e-05s
Believability | Calculation of trust value for MetaShare metadata model took 8.106231689453125e-06s
INFO | --- Analysis for metashare took 2.513474702835083s
Availability | SPARQL endpoint availability check for MExiCo took 4.124641418457031e-05s
Availability | VoID file availability check for MExiCo took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for MExiCo took 0.25312018394470215s
Reputation | Calculation of the PageRank for MExiCo took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.76837158203125e-05s
Believability | Calculation of trust value for MExiCo took 8.344650268554688e-06s
INFO | --- Analysis for mexico took 22.502182245254517s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.6000423431396484s
Availability | VoID file availability check for Coronavirus dataset took 0.0007767677307128906s
Extra | Recovery of all triples for Coronavirus dataset took 11.030219078063965s
Performance | Total latancy measurement for Coronavirus dataset took 2.456589937210083s
Amount of data | Number of triples check for Coronavirus dataset took 1.209789752960205s
Interoperability | New terms check for Coronavirus dataset took 2.4580345153808594s
Versatility | Languages check for Coronavirus dataset took 60.51734018325806s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.4842870235443115s
Interpretability | RDF structures check for Coronavirus dataset took 0.5410935878753662s
Versatility | Serialization formats check for Coronavirus dataset took 0.5554728507995605s
Availability | RDF dump link check for Coronavirus dataset took 0.4989206790924072s
License | MR license check for Coronavirus dataset took 0.5703370571136475s
License | HR license check for Coronavirus dataset took 41.36251378059387s
Amount of data | Number of property check for Coronavirus dataset took 0.5449352264404297s
Understandability | Number of label check for Coronavirus dataset took 1.6269464492797852s
Understandability | URI regex check for Coronavirus dataset took 0.9903512001037598s
Understandability | Vocabs check for Coronavirus dataset took 0.503995418548584s
Verifiability | Authors check for Coronavirus dataset took 0.5725769996643066s
Verifiability | Publishers check for Coronavirus dataset took 0.4956381320953369s
Performance | Throughput check for Coronavirus dataset took 13.90122389793396s
Amount of data | Check the number of entities for Coronavirus dataset took 0.00011014938354492188s
Verifiability | Contribs. check for Coronavirus dataset took 0.5173928737640381s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5320756435394287s
Interlinking | skos check for Coronavirus dataset took 0.551253080368042s
Interlinking | skos check for Coronavirus dataset took 0.494581937789917s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5084881782531738s
Currency | Creation date check for Coronavirus dataset took 1.031923532485962s
Currency | Modification date check for Coronavirus dataset took 1.0274114608764648s
Rep.Conc. | URIs length for Coronavirus dataset took 9.118908166885376s
Interoperability | New vocabularies check for Coronavirus dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5274708271026611s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7787823677062988s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.748476505279541s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.4793193340301514s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022562742233276367s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.029148340225219727s
Consistency | Disjoint class check for Coronavirus dataset took 1.0661561489105225s
Consistency | Check Misplaced properties for Coronavirus dataset took 8.259107112884521s
Consistency | Misplaced classes for Coronavirus dataset took 0.6326680183410645s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.9900035858154297s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.1987781524658203s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.803974628448486s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.034685611724853516s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5390915870666504s
Security | Sign check for Coronavirus dataset took 0.5287444591522217s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3139.360997200012s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.5459120273590088s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021396636962890625s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 5.9604644775390625e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 8.463859558105469e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Coronavirus dataset took 8.344650268554688e-06s
INFO | --- Analysis for micro-coronavirus took 3382.1742701530457s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.6946418285369873s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0001125335693359375s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 6.812616586685181s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.7268657684326172s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010943412780761719s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for mismuseos-gnoss took 4.904087543487549s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.1089322566986084s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2680015563964844s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.267692565917969e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.3909759521484375e-06s
INFO | --- Analysis for mlsa took 2.9989495277404785s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.220008850097656e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2782604694366455s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.8371810913085938e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 7.867813110351562e-06s
INFO | --- Analysis for model took 34.85058093070984s
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.1484832763671875e-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.0006582736968994141s
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.27356600761413574s
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.020587444305419922s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007314682006835938s
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.0994415283203125e-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 7.62939453125e-06s
INFO | --- Analysis for model1 took 17.626227617263794s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 3.933906555175781e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.2697434425354004s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020158767700195312s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.8848648071289062e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 7.62939453125e-06s
INFO | --- Analysis for mond took 3.7693021297454834s
Availability | SPARQL endpoint availability check for MONDIS took 4.553794860839844e-05s
Availability | VoID file availability check for MONDIS took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for MONDIS took 0.2808558940887451s
Reputation | Calculation of the PageRank for MONDIS took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for MONDIS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MONDIS took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.9087066650390625e-05s
Believability | Calculation of trust value for MONDIS took 8.344650268554688e-06s
INFO | --- Analysis for mondis took 2.9497063159942627s
Availability | SPARQL endpoint availability check for Monumentos took 3.981590270996094e-05s
Availability | VoID file availability check for Monumentos took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Monumentos took 0.2779221534729004s
Reputation | Calculation of the PageRank for Monumentos took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Monumentos took 2.9325485229492188e-05s
Believability | Calculation of trust value for Monumentos took 7.3909759521484375e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.8926281929016113s
Availability | SPARQL endpoint availability check for MORElab took 0.9874558448791504s
Availability | VoID file availability check for MORElab took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for MORElab took 0.24680209159851074s
Reputation | Calculation of the PageRank for MORElab took 0.02016139030456543s
Interlinking | Calculation of Degree of Connection for MORElab took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.678436279296875e-05s
Believability | Calculation of trust value for MORElab took 7.867813110351562e-06s
INFO | --- Analysis for morelab took 4.770019292831421s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.015933036804199s
Availability | VoID file availability check for Mathematics Subject Classification took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2893192768096924s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02008986473083496s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.320808410644531e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 6.67572021484375e-06s
INFO | --- Analysis for msc took 6.524583101272583s
Availability | SPARQL endpoint availability check for Multext-East took 4.100799560546875e-05s
Availability | VoID file availability check for Multext-East took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2756621837615967s
Reputation | Calculation of the PageRank for Multext-East took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for Multext-East took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.2901763916015625e-05s
Believability | Calculation of trust value for Multext-East took 7.152557373046875e-06s
INFO | --- Analysis for multext-east took 2.3943893909454346s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.935264587402344e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.2583146095275879s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.02050161361694336s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.314018249511719e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.5367431640625e-06s
INFO | --- Analysis for multilingualeulaw took 3.4204905033111572s
Availability | SPARQL endpoint availability check for Multimedia Lab took 6.961822509765625e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.27301025390625s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.4809112548828125e-05s
Believability | Calculation of trust value for Multimedia Lab took 9.059906005859375e-06s
INFO | --- Analysis for multimedia-lab took 2.9316861629486084s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.172325134277344e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0010120868682861328s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.6982643604278564s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.0040740966796875e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 7.152557373046875e-06s
INFO | --- Analysis for munich-offener-haushalt took 3.3735642433166504s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.7795522212982178s
Availability | VoID file availability check for Muninn World War I took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.267650842666626s
Reputation | Calculation of the PageRank for Muninn World War I took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.153915405273438e-05s
Believability | Calculation of trust value for Muninn World War I took 7.62939453125e-06s
INFO | --- Analysis for muninn-world-war-i took 10.458098411560059s
Availability | SPARQL endpoint availability check for Musei Italiani took 3.9577484130859375e-05s
Availability | VoID file availability check for Musei Italiani took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.27713823318481445s
Reputation | Calculation of the PageRank for Musei Italiani took 0.02028822898864746s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.9325485229492188e-05s
Believability | Calculation of trust value for Musei Italiani took 7.62939453125e-06s
INFO | --- Analysis for musei-italiani took 2.973444938659668s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.172325134277344e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.255115270614624s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010251998901367188s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for museosespania-gnoss took 3.4456357955932617s
Availability | SPARQL endpoint availability check for Italian Museums took 1.6759600639343262s
Availability | VoID file availability check for Italian Museums took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.25566744804382324s
Reputation | Calculation of the PageRank for Italian Museums took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 7.915496826171875e-05s
Believability | Calculation of trust value for Italian Museums took 7.62939453125e-06s
INFO | --- Analysis for museums-in-italy took 4.1455397605896s
Availability | SPARQL endpoint availability check for MusicBrainz took 3.910064697265625e-05s
Availability | VoID file availability check for MusicBrainz took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2738490104675293s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020314455032348633s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 2.9087066650390625e-05s
Believability | Calculation of trust value for MusicBrainz took 6.9141387939453125e-06s
INFO | --- Analysis for musicbrainz_ took 2.9086270332336426s
Availability | SPARQL endpoint availability check for MusicNet Codex took 3.9577484130859375e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.2689976692199707s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020050764083862305s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.9087066650390625e-05s
Believability | Calculation of trust value for MusicNet Codex took 6.9141387939453125e-06s
INFO | --- Analysis for musicnet_codex took 2.8994669914245605s
Availability | SPARQL endpoint availability check for Muziekweb took 0.6790008544921875s
Availability | VoID file availability check for Muziekweb took 0.0006361007690429688s
Extra | Recovery of all triples for Muziekweb took 2.0101799964904785s
Performance | Total latancy measurement for Muziekweb took 1.4120144844055176s
Amount of data | Number of triples check for Muziekweb took 0.37173962593078613s
Interoperability | New terms check for Muziekweb took 1.5711421966552734s
Versatility | Languages check for Muziekweb took 49.135387659072876s
Interpretability | Number of blank nodes check for Muziekweb took 0.30096960067749023s
Interpretability | RDF structures check for Muziekweb took 0.7696058750152588s
Versatility | Serialization formats check for Muziekweb took 0.32123613357543945s
Availability | RDF dump link check for Muziekweb took 0.2949976921081543s
License | MR license check for Muziekweb took 0.25914549827575684s
License | HR license check for Muziekweb took 11.457810878753662s
Amount of data | Number of property check for Muziekweb took 0.30953454971313477s
Understandability | Number of label check for Muziekweb took 0.3590118885040283s
Understandability | URI regex check for Muziekweb took 0.5476667881011963s
Understandability | Vocabs check for Muziekweb took 0.2608811855316162s
Verifiability | Authors check for Muziekweb took 0.3046226501464844s
Verifiability | Publishers check for Muziekweb took 0.29206275939941406s
Performance | Throughput check for Muziekweb took 11.373044729232788s
Amount of data | Check the number of entities for Muziekweb took 6.985664367675781e-05s
Verifiability | Contribs. check for Muziekweb took 0.2914607524871826s
Interlinking | sameAs chians check for Muziekweb took 0.32031822204589844s
Interlinking | skos check for Muziekweb took 0.2792336940765381s
Interlinking | skos check for Muziekweb took 0.28350329399108887s
Timeliness | dataset update frequency check for Muziekweb took 0.30602502822875977s
Currency | Creation date check for Muziekweb took 0.6929726600646973s
Currency | Modification date check for Muziekweb took 0.657174825668335s
Rep.Conc. | URIs length for Muziekweb took 2.0025718212127686s
Interoperability | New vocabularies check for Muziekweb took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.2729971408843994s
Accuracy | Check Functional Property for Muziekweb took 0.3845505714416504s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.34743332862854004s
Accuracy | Check Empty annotation labels for Muziekweb took 3.612541437149048s
Accuracy | Check White space in annotation for Muziekweb took 0.027591466903686523s
Accuracy | Check Datatype consistency for Muziekweb took 0.029123783111572266s
Consistency | Disjoint class check for Muziekweb took 0.6023454666137695s
Consistency | Check Misplaced properties for Muziekweb took 1.1495020389556885s
Consistency | Check Ontology hijacking for Muziekweb took 1.9281001091003418s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.9989042282104492s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.4670121669769287s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03333854675292969s
Conciseness | Check Intensional conciseness for Muziekweb took 0.31961536407470703s
Security | Sign check for Muziekweb took 0.32509326934814453s
Availability | Check URIs Dereferenciability for Muziekweb took 1724.9780178070068s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.3962068557739258s
Reputation | Calculation of the PageRank for Muziekweb took 0.021199464797973633s
Interlinking | Calculation of Degree of Connection for Muziekweb took 7.271766662597656e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.508827209472656e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.430511474609375e-06s
Believability | Calculation of trust value for Muziekweb took 8.344650268554688e-06s
INFO | --- Analysis for muziekweb took 1851.3432977199554s
Availability | SPARQL endpoint availability check for myExperiment took 0.31692051887512207s
Availability | VoID file availability check for myExperiment took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for myExperiment took 0.7136812210083008s
Reputation | Calculation of the PageRank for myExperiment took 0.02082061767578125s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0009777545928955078s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00011563301086425781s
Believability | Calculation of trust value for myExperiment took 8.58306884765625e-06s
INFO | --- Analysis for my-experiment took 4.670517444610596s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.07124900817871094s
Availability | VoID file availability check for My Family Lineage took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2618842124938965s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.463859558105469e-05s
Believability | Calculation of trust value for My Family Lineage took 7.867813110351562e-06s
INFO | --- Analysis for my-family-lineage took 4.8921473026275635s
Availability | SPARQL endpoint availability check for My ontology test took 0.4963221549987793s
Availability | VoID file availability check for My ontology test took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for My ontology test took 0.2741279602050781s
Reputation | Calculation of the PageRank for My ontology test took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.123283386230469e-05s
Believability | Calculation of trust value for My ontology test took 7.867813110351562e-06s
INFO | --- Analysis for myontologytest took 4.604940176010132s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.172325134277344e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.2726621627807617s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 9.870529174804688e-05s
Believability | Calculation of trust value for myopenlink dataspaces took 8.344650268554688e-06s
INFO | --- Analysis for myopenlink-dataspaces took 2.7374486923217773s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 5.2409186363220215s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.7102663516998291s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.508827209472656e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 6.4373016357421875e-06s
INFO | --- Analysis for n-lex-as-linked-data took 13.372854948043823s
Availability | SPARQL endpoint availability check for NAICS 2007 took 163.23420643806458s
Availability | VoID file availability check for NAICS 2007 took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.28193116188049316s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 5.364418029785156e-05s
Believability | Calculation of trust value for NAICS 2007 took 6.198883056640625e-06s
INFO | --- Analysis for naics-2007 took 480.4991557598114s
Availability | SPARQL endpoint availability check for NAICS 2012 took 35.96123957633972s
Availability | VoID file availability check for NAICS 2012 took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 1.1941182613372803s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 0.00011372566223144531s
Believability | Calculation of trust value for NAICS 2012 took 5.7220458984375e-06s
INFO | --- Analysis for naics-2012 took 356.09303975105286s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.26728200912475586s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02065253257751465s
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.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 4.839897155761719e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for nalt took 4.742659091949463s
Availability | SPARQL endpoint availability check for Usernames  took 4.0531158447265625e-05s
Availability | VoID file availability check for Usernames  took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Usernames  took 0.2610132694244385s
Reputation | Calculation of the PageRank for Usernames  took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Usernames  took 2.8371810913085938e-05s
Believability | Calculation of trust value for Usernames  took 7.867813110351562e-06s
INFO | --- Analysis for Names took 2.349109649658203s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.3337914943695068s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0006852149963378906s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.0312039852142334s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.9013392925262451s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 13.100714445114136s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 28.506223440170288s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.38775062561035156s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 14.53091549873352s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.7999932765960693s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.38236236572265625s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.35300207138061523s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.38770151138305664s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3727993965148926s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.77745985984802s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9279849529266357s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 8.190110683441162s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7417125701904297s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.38573741912841797s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.3896636962890625s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.406327486038208s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.542884349822998s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 0.00012636184692382812s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.40552568435668945s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.597440242767334s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 2.153094530105591s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.1072514057159424s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3967921733856201s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.163069725036621s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.8363590240478516s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.050731897354126s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.3807542324066162s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3580169677734375s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3885538578033447s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.40560054779052734s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007491111755371094s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010304450988769531s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.3497788906097412s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.8224499225616455s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.42553162574768066s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.5582799911499023s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.1632108688354492s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.5357530117034912s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0005981922149658203s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3872334957122803s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 3.7997379302978516s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.2811737060546875s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.430511474609375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 5.4836273193359375e-06s
INFO | --- Analysis for national-diet-library-authorities took 245.62005996704102s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.37502193450927734s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005810260772705078s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.5002846717834473s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.9915361404418945s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.959911108016968s
Interoperability | New terms check for National Diet Library of Japan subject headings took 20.200146436691284s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.35798096656799316s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.715747833251953s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.37852001190185547s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3910667896270752s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.4296000003814697s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.36913204193115234s
License | MR license check for National Diet Library of Japan subject headings took 0.4086642265319824s
License | HR license check for National Diet Library of Japan subject headings took 91.79175996780396s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8902535438537598s
Understandability | Number of label check for National Diet Library of Japan subject headings took 7.349791526794434s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7188920974731445s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.38517284393310547s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3744685649871826s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3367321491241455s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.579353332519531s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.630752563476562e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.36378002166748047s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.47011423110961914s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.4055373668670654s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.0475804805755615s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.35107970237731934s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1527767181396484s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.781341552734375s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 1.0495426654815674s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.36702442169189453s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.36197519302368164s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3885471820831299s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.3921232223510742s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0008172988891601562s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010666847229003906s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.35288190841674805s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.8071541786193848s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3675053119659424s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.5603666305541992s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.1967017650604248s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.5394408702850342s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006775856018066406s
Security | Sign check for National Diet Library of Japan subject headings took 0.4037642478942871s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 4.027096509933472s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.8143799304962158s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02122044563293457s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0011029243469238281s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 9.465217590332031e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 2.384185791015625e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 8.344650268554688e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 231.72142791748047s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.09739089012146s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.28466248512268066s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.4345855712890625e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 6.4373016357421875e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 6.46413779258728s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.172325134277344e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2531442642211914s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.961822509765625e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.152557373046875e-06s
INFO | --- Analysis for Naturopathy took 3.832207679748535s
Availability | SPARQL endpoint availability check for Naturopathy took 4.029273986816406e-05s
Availability | VoID file availability check for Naturopathy took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.2562289237976074s
Reputation | Calculation of the PageRank for Naturopathy took 0.021391630172729492s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.2901763916015625e-05s
Believability | Calculation of trust value for Naturopathy took 8.106231689453125e-06s
INFO | --- Analysis for naturopathy2 took 4.260641098022461s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 5.650520324707031e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.28012776374816895s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.123283386230469e-05s
Believability | Calculation of trust value for NCI Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for nci-thesaurus took 2.8994364738464355s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.446699857711792s
Availability | VoID file availability check for COVID-19 Data took 0.0003161430358886719s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.25199222564697266s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.0214998722076416s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.24249267578125e-05s
Believability | Calculation of trust value for COVID-19 Data took 7.867813110351562e-06s
INFO | --- Analysis for NCMI-COVID-19 took 7.298228740692139s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.409912347793579s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.2788527011871338s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020882606506347656s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.811981201171875e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 7.62939453125e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.208106279373169s
Availability | SPARQL endpoint availability check for NDF-RT took 4.220008850097656e-05s
Availability | VoID file availability check for NDF-RT took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.2772095203399658s
Reputation | Calculation of the PageRank for NDF-RT took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.1948089599609375e-05s
Believability | Calculation of trust value for NDF-RT took 8.821487426757812e-06s
INFO | --- Analysis for ndf-rt took 2.9003312587738037s
Availability | SPARQL endpoint availability check for Near took 4.267692565917969e-05s
Availability | VoID file availability check for Near took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Near took 0.27090954780578613s
Reputation | Calculation of the PageRank for Near took 0.020750045776367188s
Interlinking | Calculation of Degree of Connection for Near took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Near took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Near took 9.059906005859375e-05s
Believability | Calculation of trust value for Near took 8.106231689453125e-06s
INFO | --- Analysis for near took 15.785430908203125s
Availability | SPARQL endpoint availability check for Neel took 4.029273986816406e-05s
Availability | VoID file availability check for Neel took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Neel took 0.26097583770751953s
Reputation | Calculation of the PageRank for Neel took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for Neel took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neel took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Neel took 3.075599670410156e-05s
Believability | Calculation of trust value for Neel took 7.867813110351562e-06s
INFO | --- Analysis for neel took 2.8981943130493164s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.124641418457031e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.2617776393890381s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.02033829689025879s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.147125244140625e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 7.867813110351562e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.8909928798675537s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.172325134277344e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2735891342163086s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.266334533691406e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 9.059906005859375e-06s
INFO | --- Analysis for neurolex-wiki took 2.325312852859497s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.172325134277344e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0004177093505859375s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.24572062492370605s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.458427429199219e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 7.867813110351562e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.5443782806396484s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.00042319297790527344s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.26183557510375977s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 7.05718994140625e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 8.821487426757812e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.423511743545532s
Availability | SPARQL endpoint availability check for Newsweek took 4.00543212890625e-05s
Availability | VoID file availability check for Newsweek took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Newsweek took 0.2589402198791504s
Reputation | Calculation of the PageRank for Newsweek took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.075599670410156e-05s
Believability | Calculation of trust value for Newsweek took 8.58306884765625e-06s
INFO | --- Analysis for newsweek took 2.8243837356567383s
Availability | SPARQL endpoint availability check for neXtProt took 1.5135314464569092s
Availability | VoID file availability check for neXtProt took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for neXtProt took 0.25571775436401367s
Reputation | Calculation of the PageRank for neXtProt took 0.02082061767578125s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.886222839355469e-05s
Believability | Calculation of trust value for neXtProt took 8.821487426757812e-06s
INFO | --- Analysis for nextprot took 4.51700758934021s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.506111145019531e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2661733627319336s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.021350860595703125s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010347366333007812s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 8.58306884765625e-06s
INFO | --- Analysis for nextweb-gnoss took 4.726738691329956s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.172325134277344e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.25910162925720215s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02133655548095703s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.392333984375e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 6.9141387939453125e-06s
INFO | --- Analysis for nhs-jargon took 2.7602574825286865s
Availability | SPARQL endpoint availability check for NIT Patna took 8.058547973632812e-05s
Availability | VoID file availability check for NIT Patna took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.2761693000793457s
Reputation | Calculation of the PageRank for NIT Patna took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.794929504394531e-05s
Believability | Calculation of trust value for NIT Patna took 9.298324584960938e-06s
INFO | --- Analysis for NITP took 3.4068644046783447s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 5.3882598876953125e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00032210350036621094s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.26940202713012695s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.647804260253906e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 8.58306884765625e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.9652302265167236s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.27158689498901367s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.147125244140625e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 8.58306884765625e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.052397727966309s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5094685554504395s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2548649311065674s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 8.821487426757812e-06s
INFO | --- Analysis for NLW took 4.013870716094971s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.425321102142334s
Availability | VoID file availability check for Nobel Prizes took 0.0013279914855957031s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.265669584274292s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.298324584960938e-05s
Believability | Calculation of trust value for Nobel Prizes took 8.106231689453125e-06s
INFO | --- Analysis for nobelprizes took 8.335073947906494s
Availability | SPARQL endpoint availability check for NoiPA took 0.3203902244567871s
Availability | VoID file availability check for NoiPA took 0.0002639293670654297s
Extra | Recovery of all triples for NoiPA took 82.74701404571533s
Performance | Total latancy measurement for NoiPA took 0.630237340927124s
Amount of data | Number of triples check for NoiPA took 1.4295845031738281s
Interoperability | New terms check for NoiPA took 2.856337547302246s
Versatility | Languages check for NoiPA took 60.164116859436035s
Interpretability | Number of blank nodes check for NoiPA took 0.16473793983459473s
Interpretability | RDF structures check for NoiPA took 0.17127704620361328s
Versatility | Serialization formats check for NoiPA took 0.1755356788635254s
Availability | RDF dump link check for NoiPA took 0.1996464729309082s
License | MR license check for NoiPA took 0.24083828926086426s
License | HR license check for NoiPA took 60.1835241317749s
Amount of data | Number of property check for NoiPA took 0.1552879810333252s
Understandability | Number of label check for NoiPA took 0.5802288055419922s
Understandability | URI regex check for NoiPA took 0.5355315208435059s
Understandability | Vocabs check for NoiPA took 0.15279436111450195s
Verifiability | Authors check for NoiPA took 0.13651108741760254s
Verifiability | Publishers check for NoiPA took 0.11417889595031738s
Performance | Throughput check for NoiPA took 10.764866590499878s
Amount of data | Check the number of entities for NoiPA took 7.724761962890625e-05s
Verifiability | Contribs. check for NoiPA took 0.18752503395080566s
Interlinking | sameAs chians check for NoiPA took 0.11847519874572754s
Interlinking | skos check for NoiPA took 0.652310848236084s
Interlinking | skos check for NoiPA took 0.1423485279083252s
Timeliness | dataset update frequency check for NoiPA took 0.10637760162353516s
Currency | Creation date check for NoiPA took 0.250072717666626s
Currency | Modification date check for NoiPA took 0.2139873504638672s
Rep.Conc. | URIs length for NoiPA took 52.92163443565369s
Interoperability | New vocabularies check for NoiPA took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.11193585395812988s
Accuracy | Check Functional Property for NoiPA took 0.21142292022705078s
Accuracy | Check Inverse Functional Property for NoiPA took 0.18539953231811523s
Accuracy | Check Empty annotation labels for NoiPA took 25.29471778869629s
Accuracy | Check White space in annotation for NoiPA took 2.237478256225586s
Accuracy | Check Datatype consistency for NoiPA took 2.013862133026123s
Consistency | Disjoint class check for NoiPA took 0.148268461227417s
Consistency | Check Misplaced properties for NoiPA took 19.3857479095459s
Consistency | Misplaced classes for NoiPA took 6.17723274230957s
Consistency | Check Ontology hijacking for NoiPA took 22.6655330657959s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.5691108703613281s
Consistency | Check Invalid usage of undefined properties for NoiPA took 20.480680465698242s
Conciseness | Check Extensional conciseness for NoiPA took 2.1638362407684326s
Conciseness | Check Intensional conciseness for NoiPA took 0.10992860794067383s
Security | Sign check for NoiPA took 0.18917417526245117s
Availability | Check URIs Dereferenciability for NoiPA took 8.697317123413086s
Completeness | Calculation of interlinking completeness for NoiPA took 1.0487287044525146s
Reputation | Calculation of the PageRank for NoiPA took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.0279159545898438e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 2.1457672119140625e-06s
Believability | Calculation of trust value for NoiPA took 7.867813110351562e-06s
INFO | --- Analysis for NoiPA took 567.0747129917145s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.913244962692261s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.7016351222991943s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.465217590332031e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 6.67572021484375e-06s
INFO | --- Analysis for nom took 22.011000394821167s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 26.403818368911743s
Availability | VoID file availability check for Nomenclator Asturias took 0.0009248256683349609s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.72355055809021s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.021143198013305664s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.797645568847656e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 6.198883056640625e-06s
INFO | --- Analysis for nomenclator-asturias took 267.23411202430725s
Availability | SPARQL endpoint availability check for nomisma took 4.0531158447265625e-05s
Availability | VoID file availability check for nomisma took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for nomisma took 0.26990222930908203s
Reputation | Calculation of the PageRank for nomisma took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for nomisma took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.2901763916015625e-05s
Believability | Calculation of trust value for nomisma took 8.106231689453125e-06s
INFO | --- Analysis for nomisma took 4.774694204330444s
Availability | SPARQL endpoint availability check for Nomisma.org  took 1.1943731307983398s
Availability | VoID file availability check for Nomisma.org  took 0.0003619194030761719s
Extra | Recovery of all triples for Nomisma.org  took 661.8322062492371s
Performance | Total latancy measurement for Nomisma.org  took 1.594477653503418s
Amount of data | Number of triples check for Nomisma.org  took 48.530874490737915s
Interoperability | New terms check for Nomisma.org  took 10.310312747955322s
Versatility | Languages check for Nomisma.org  took 112.47113394737244s
Interpretability | Number of blank nodes check for Nomisma.org  took 55.06051063537598s
Security | Check HTTPS for Nomisma.org  took 0.8289000988006592s
Interpretability | RDF structures check for Nomisma.org  took 0.3237333297729492s
Versatility | Serialization formats check for Nomisma.org  took 0.33516359329223633s
Availability | RDF dump link check for Nomisma.org  took 1250.0865371227264s
License | MR license check for Nomisma.org  took 0.3677992820739746s
License | HR license check for Nomisma.org  took 59.2742121219635s
Amount of data | Number of property check for Nomisma.org  took 0.37308573722839355s
Understandability | Number of label check for Nomisma.org  took 11.169299125671387s
Understandability | URI regex check for Nomisma.org  took 0.7288699150085449s
Understandability | Vocabs check for Nomisma.org  took 0.3261849880218506s
Verifiability | Authors check for Nomisma.org  took 0.3069319725036621s
Verifiability | Publishers check for Nomisma.org  took 0.4297163486480713s
Performance | Throughput check for Nomisma.org  took 11.876294136047363s
Amount of data | Check the number of entities for Nomisma.org  took 64.72850036621094s
Verifiability | Contribs. check for Nomisma.org  took 0.5594234466552734s
Interlinking | sameAs chians check for Nomisma.org  took 0.3281524181365967s
Interlinking | skos check for Nomisma.org  took 1.0807480812072754s
Interlinking | skos check for Nomisma.org  took 0.504347562789917s
Timeliness | dataset update frequency check for Nomisma.org  took 0.30439090728759766s
Currency | Creation date check for Nomisma.org  took 0.6557202339172363s
Currency | Modification date check for Nomisma.org  took 0.33699679374694824s
Rep.Conc. | URIs length for Nomisma.org  took 296.2771189212799s
Interoperability | New vocabularies check for Nomisma.org  took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.3782198429107666s
Accuracy | Check Functional Property for Nomisma.org  took 0.3262596130371094s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3094303607940674s
Accuracy | Check Empty annotation labels for Nomisma.org  took 212.98030948638916s
Accuracy | Check White space in annotation for Nomisma.org  took 2.7894906997680664s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.412838459014893s
Consistency | Disjoint class check for Nomisma.org  took 0.33719420433044434s
Consistency | Check Misplaced properties for Nomisma.org  took 26.450525283813477s
Consistency | Check Ontology hijacking for Nomisma.org  took 235.1660599708557s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 1.787827968597412s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 28.897013425827026s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.7696094512939453s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.35720396041870117s
Security | Sign check for Nomisma.org  took 0.3197033405303955s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1785.2038543224335s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.4927952289581299s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.021963834762573242s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0009222030639648438s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 0.00014710426330566406s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 2.384185791015625e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.1444091796875e-05s
INFO | --- Analysis for nomisma_org took 9172.384019136429s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.3226327896118164s
Availability | VoID file availability check for Curriculum Vitae took 0.00025272369384765625s
Extra | Recovery of all triples for Curriculum Vitae took 0.6223983764648438s
Performance | Total latancy measurement for Curriculum Vitae took 1.2072579860687256s
Amount of data | Number of triples check for Curriculum Vitae took 0.11769366264343262s
Interoperability | New terms check for Curriculum Vitae took 1.419306755065918s
Versatility | Languages check for Curriculum Vitae took 0.20328593254089355s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.20428085327148438s
Interpretability | RDF structures check for Curriculum Vitae took 0.13248586654663086s
Versatility | Serialization formats check for Curriculum Vitae took 0.10898065567016602s
Availability | RDF dump link check for Curriculum Vitae took 0.2054438591003418s
License | MR license check for Curriculum Vitae took 0.10950994491577148s
License | HR license check for Curriculum Vitae took 0.11916041374206543s
Amount of data | Number of property check for Curriculum Vitae took 0.13203072547912598s
Understandability | Number of label check for Curriculum Vitae took 0.11078572273254395s
Understandability | URI regex check for Curriculum Vitae took 0.29798340797424316s
Understandability | Vocabs check for Curriculum Vitae took 0.19974756240844727s
Verifiability | Authors check for Curriculum Vitae took 0.21951532363891602s
Verifiability | Publishers check for Curriculum Vitae took 0.10428738594055176s
Performance | Throughput check for Curriculum Vitae took 10.536307096481323s
Amount of data | Check the number of entities for Curriculum Vitae took 0.00010657310485839844s
Verifiability | Contribs. check for Curriculum Vitae took 0.11580538749694824s
Interlinking | sameAs chians check for Curriculum Vitae took 0.1050875186920166s
Interlinking | skos check for Curriculum Vitae took 0.10422730445861816s
Interlinking | skos check for Curriculum Vitae took 0.1967778205871582s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.19982242584228516s
Currency | Creation date check for Curriculum Vitae took 0.4097001552581787s
Currency | Modification date check for Curriculum Vitae took 0.31159496307373047s
Rep.Conc. | URIs length for Curriculum Vitae took 0.37305784225463867s
Interoperability | New vocabularies check for Curriculum Vitae took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.30399155616760254s
Accuracy | Check Functional Property for Curriculum Vitae took 0.19688916206359863s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.10479402542114258s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.1953749656677246s
Accuracy | Check White space in annotation for Curriculum Vitae took 9.083747863769531e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0020678043365478516s
Consistency | Disjoint class check for Curriculum Vitae took 0.2053384780883789s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.4867403507232666s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.497037410736084s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.4561777114868164s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.6849501132965088s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0013153553009033203s
Security | Sign check for Curriculum Vitae took 0.20394444465637207s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.16832733154297s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.6954748630523682s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 2.9087066650390625e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 9.5367431640625e-07s
Believability | Calculation of trust value for Curriculum Vitae took 7.867813110351562e-06s
INFO | --- Analysis for Nordine_Bittich took 58.62178587913513s
Availability | SPARQL endpoint availability check for NorPark took 2.0330636501312256s
Availability | VoID file availability check for NorPark took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for NorPark took 0.6773872375488281s
Reputation | Calculation of the PageRank for NorPark took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.76837158203125e-05s
Believability | Calculation of trust value for NorPark took 8.344650268554688e-06s
INFO | --- Analysis for norpark took 5.708873987197876s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.023454666137695312s
Availability | VoID file availability check for Parking Dataset took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2468717098236084s
Reputation | Calculation of the PageRank for Parking Dataset took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.3392181396484375e-05s
Believability | Calculation of trust value for Parking Dataset took 6.67572021484375e-06s
INFO | --- Analysis for norpark2 took 2.7039685249328613s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.5490384101867676s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0002453327178955078s
Extra | Recovery of all triples for Norway fishery stocks dataset took 118.81179332733154s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.8959221839904785s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.05399465560913s
Interoperability | New terms check for Norway fishery stocks dataset took 14.275794506072998s
Versatility | Languages check for Norway fishery stocks dataset took 300.180969953537s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 3.3789312839508057s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.2490096092224121s
Versatility | Serialization formats check for Norway fishery stocks dataset took 11.118031740188599s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.21477222442626953s
License | MR license check for Norway fishery stocks dataset took 0.47255802154541016s
License | HR license check for Norway fishery stocks dataset took 300.2371406555176s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.37532854080200195s
Understandability | Number of label check for Norway fishery stocks dataset took 2.9093782901763916s
Understandability | URI regex check for Norway fishery stocks dataset took 0.7673401832580566s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.42202091217041016s
Verifiability | Authors check for Norway fishery stocks dataset took 0.18675994873046875s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.24785375595092773s
Performance | Throughput check for Norway fishery stocks dataset took 10.713431119918823s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 6.67572021484375e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.18293452262878418s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.18636012077331543s
Interlinking | skos check for Norway fishery stocks dataset took 0.4567115306854248s
Interlinking | skos check for Norway fishery stocks dataset took 0.43448615074157715s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 5.3371734619140625s
Currency | Creation date check for Norway fishery stocks dataset took 0.45224571228027344s
Currency | Modification date check for Norway fishery stocks dataset took 0.2218794822692871s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 162.24556398391724s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.1760258674621582s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.27597808837890625s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.27722620964050293s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 39.47373986244202s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.665703058242798s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.6396610736846924s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.1815962791442871s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 96.77044486999512s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.315495252609253s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 36.47837996482849s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.2019786834716797s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 93.90638995170593s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7946689128875732s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5994665622711182s
Security | Sign check for Norway fishery stocks dataset took 0.6121041774749756s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 18.345569849014282s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 1.22892165184021s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.02133488655090332s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 6.628036499023438e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 7.152557373046875e-06s
INFO | --- Analysis for Norway_Fishery_ took 2282.7892458438873s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.45587635040283203s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0003952980041503906s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.23501849174499512s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.649162292480469e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 8.821487426757812e-06s
INFO | --- Analysis for norwegian-geo-divisions took 8.676364660263062s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.00543212890625e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.2429182529449463s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.021472692489624023s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.1948089599609375e-05s
Believability | Calculation of trust value for NorwegianSoE took 8.344650268554688e-06s
INFO | --- Analysis for norwegiansoe took 4.036635398864746s
Availability | SPARQL endpoint availability check for NITP took 7.462501525878906e-05s
Availability | VoID file availability check for NITP took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for NITP took 0.2521979808807373s
Reputation | Calculation of the PageRank for NITP took 0.020648717880249023s
Interlinking | Calculation of Degree of Connection for NITP took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for NITP took 6.771087646484375e-05s
Believability | Calculation of trust value for NITP took 9.298324584960938e-06s
INFO | --- Analysis for notIdentifier took 3.9054012298583984s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.00543212890625e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.24692678451538086s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02066659927368164s
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.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.647804260253906e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 8.344650268554688e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.040297746658325s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.029273986816406e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.25232362747192383s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.0517578125e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 8.106231689453125e-06s
INFO | --- Analysis for npg took 2.707158088684082s
Availability | SPARQL endpoint availability check for NPM took 4.410743713378906e-05s
Availability | VoID file availability check for NPM took 0.00035881996154785156s
Completeness | Calculation of interlinking completeness for NPM took 0.24580836296081543s
Reputation | Calculation of the PageRank for NPM took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for NPM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for NPM took 3.600120544433594e-05s
Believability | Calculation of trust value for NPM took 8.344650268554688e-06s
INFO | --- Analysis for npm took 2.995598793029785s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.036310672760009766s
Availability | VoID file availability check for NTNU special collections took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.24336957931518555s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.6743621826171875e-05s
Believability | Calculation of trust value for NTNU special collections took 8.821487426757812e-06s
INFO | --- Analysis for ntnusc took 4.768664360046387s
Availability | SPARQL endpoint availability check for links took 4.172325134277344e-05s
Availability | VoID file availability check for links took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for links took 0.2480297088623047s
Reputation | Calculation of the PageRank for links took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for links took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for links took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for links took 1.3113021850585938e-05s
Believability | Calculation of trust value for links took 9.059906005859375e-06s
INFO | --- Analysis for nugmyanmar took 2.1936588287353516s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.315376281738281e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.25696253776550293s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.751319885253906e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 7.3909759521484375e-06s
INFO | --- Analysis for nuts-geovocab took 5.828282356262207s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.37115478515625s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.2470104694366455s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.866455078125e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 8.821487426757812e-06s
INFO | --- Analysis for nvd took 3.6572015285491943s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 1.0722112655639648s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.24875783920288086s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 9.584426879882812e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 8.344650268554688e-06s
INFO | --- Analysis for nvs took 8.177103281021118s
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.00047469139099121094s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.24875831604003906s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00017952919006347656s
Believability | Calculation of trust value for New York Times - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.2607109546661377s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.00543212890625e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.24880146980285645s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.218650817871094e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 9.298324584960938e-06s
INFO | --- Analysis for o-anc took 2.680968761444092s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.458427429199219e-05s
Availability | VoID file availability check for OANetzwerk took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.24955081939697266s
Reputation | Calculation of the PageRank for OANetzwerk took 0.02071547508239746s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.123283386230469e-05s
Believability | Calculation of trust value for OANetzwerk took 9.298324584960938e-06s
INFO | --- Analysis for oanetzwerk took 2.6810269355773926s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.172325134277344e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.24073100090026855s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.218650817871094e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 1.0728836059570312e-05s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.6888914108276367s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.4838435649871826s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0007035732269287109s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.643153429031372s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 2.8435046672821045s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 4.850543737411499s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7519383430480957s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.298521280288696s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.7376549243927s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.22398042678833008s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.37578725814819336s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.3817024230957031s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.37232303619384766s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.437974214553833s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.21316123008728s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.3003518581390381s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.6637136936187744s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.571340799331665s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.3862464427947998s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.3851766586303711s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3238649368286133s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.169619083404541s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 6.842613220214844e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.2971038818359375s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.32834887504577637s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3040132522583008s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.2980341911315918s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.3734629154205322s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.5362436771392822s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.23875832557678223s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 18.092589378356934s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.2980937957763672s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.30094003677368164s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.29703354835510254s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.9033310413360596s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.023505687713623047s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.02994227409362793s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.32315564155578613s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.390803098678589s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.35645413398742676s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 1.8641674518585205s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.1398208141326904s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 14.367669105529785s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.031206846237182617s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.36348676681518555s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3032083511352539s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 22.069157361984253s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3060758113861084s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.274482727050781e-05s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 6.67572021484375e-06s
INFO | --- Analysis for ocd took 387.172119140625s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.267692565917969e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.24937224388122559s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.02024364471435547s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.790855407714844e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-borehole took 3.869154691696167s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.2328283786773682s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.24909734725952148s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020386457443237305s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.153915405273438e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 9.298324584960938e-06s
INFO | --- Analysis for oceandrilling-codices took 6.86371374130249s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.0547163486480713s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2583577632904053s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.147125244140625e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 7.067704200744629s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.015704870223999s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.24845433235168457s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02024698257446289s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.337860107421875e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 8.344650268554688e-06s
INFO | --- Analysis for oceandrilling-forams took 5.950389623641968s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.0514824390411377s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.25295305252075195s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.552436828613281e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-janus took 5.227571249008179s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 10.978602886199951s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0008285045623779297s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.24964141845703125s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020716428756713867s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.600120544433594e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-janusamp took 15.191148519515991s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0522093772888184s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007297992706298828s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.24975872039794922s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020941734313964844s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.0517578125e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-ldeo took 5.253810167312622s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.1961669921875e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2515134811401367s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020972490310668945s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.459785461425781e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 8.106231689453125e-06s
INFO | --- Analysis for oclc-fast took 6.944688558578491s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.00543212890625e-05s
Availability | VoID file availability check for Open Data Communities took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.24825668334960938s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Data Communities took 8.821487426757812e-06s
INFO | --- Analysis for odc took 2.717651605606079s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 7.939338684082031e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.24774599075317383s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.9802322387695312e-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 2.974057674407959s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 3.9577484130859375e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2488715648651123s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.021585702896118164s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 3.123283386230469e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 5.9604644775390625e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.702852964401245s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.23679590225219727s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2519402503967285s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.528594970703125e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.245208740234375e-06s
INFO | --- Analysis for odc-lsoa took 3.5504329204559326s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.076957702636719e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.26082324981689453s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.9802322387695312e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 7.3909759521484375e-06s
INFO | --- Analysis for odc-population-2005 took 2.6990160942077637s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.124641418457031e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2405714988708496s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 7.62939453125e-06s
INFO | --- Analysis for ods took 2.6804773807525635s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.3508262634277344s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.24845576286315918s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.512901306152344e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for oecd-linked-data took 2.5971310138702393s
Availability | SPARQL endpoint availability check for Offener Haushalt took 3.910064697265625e-05s
Availability | VoID file availability check for Offener Haushalt took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.24713945388793945s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.0040740966796875e-05s
Believability | Calculation of trust value for Offener Haushalt took 6.4373016357421875e-06s
INFO | --- Analysis for offener-haushalt took 2.685821533203125s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.151105642318726s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.25010108947753906s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 5.245208740234375e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 8.344650268554688e-06s
INFO | --- Analysis for ogolod took 102.83844113349915s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.6253204345703125e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.25022244453430176s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.528594970703125e-05s
Believability | Calculation of trust value for OLAC Metadata took 8.106231689453125e-06s
INFO | --- Analysis for olac took 23.344871759414673s
Availability | SPARQL endpoint availability check for OLiA took 4.2438507080078125e-05s
Availability | VoID file availability check for OLiA took 0.0007979869842529297s
Completeness | Calculation of interlinking completeness for OLiA took 0.24570560455322266s
Reputation | Calculation of the PageRank for OLiA took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for OLiA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00011658668518066406s
Believability | Calculation of trust value for OLiA took 7.152557373046875e-06s
INFO | --- Analysis for olia took 15.453304529190063s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.267692565917969e-05s
Availability | VoID file availability check for OLiA Discourse took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2502865791320801s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020153522491455078s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.528594970703125e-05s
Believability | Calculation of trust value for OLiA Discourse took 7.867813110351562e-06s
INFO | --- Analysis for olia-discourse took 8.89263653755188s
Availability | SPARQL endpoint availability check for Open Land Use took 0.26929140090942383s
Availability | VoID file availability check for Open Land Use took 0.00026679039001464844s
Extra | Recovery of all triples for Open Land Use took 122.691481590271s
Performance | Total latancy measurement for Open Land Use took 0.8850252628326416s
Amount of data | Number of triples check for Open Land Use took 8.490626335144043s
Interoperability | New terms check for Open Land Use took 14.711407661437988s
Versatility | Languages check for Open Land Use took 300.19925928115845s
Interpretability | Number of blank nodes check for Open Land Use took 1.8993926048278809s
Interpretability | RDF structures check for Open Land Use took 0.21637582778930664s
Versatility | Serialization formats check for Open Land Use took 9.649401903152466s
Availability | RDF dump link check for Open Land Use took 0.2252185344696045s
License | MR license check for Open Land Use took 0.37506628036499023s
License | HR license check for Open Land Use took 300.23030400276184s
Amount of data | Number of property check for Open Land Use took 0.282132625579834s
Understandability | Number of label check for Open Land Use took 2.9387524127960205s
Understandability | URI regex check for Open Land Use took 0.841498851776123s
Understandability | Vocabs check for Open Land Use took 0.4497356414794922s
Verifiability | Authors check for Open Land Use took 0.1995410919189453s
Verifiability | Publishers check for Open Land Use took 0.261904239654541s
Performance | Throughput check for Open Land Use took 11.434360980987549s
Amount of data | Check the number of entities for Open Land Use took 7.200241088867188e-05s
Verifiability | Contribs. check for Open Land Use took 0.20045900344848633s
Interlinking | sameAs chians check for Open Land Use took 0.17908477783203125s
Interlinking | skos check for Open Land Use took 0.4421195983886719s
Interlinking | skos check for Open Land Use took 0.43802762031555176s
Timeliness | dataset update frequency check for Open Land Use took 5.777939796447754s
Currency | Creation date check for Open Land Use took 0.4857006072998047s
Currency | Modification date check for Open Land Use took 0.23750758171081543s
Rep.Conc. | URIs length for Open Land Use took 166.65095019340515s
Interoperability | New vocabularies check for Open Land Use took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.18026137351989746s
Accuracy | Check Functional Property for Open Land Use took 0.34331274032592773s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.3452756404876709s
Accuracy | Check Empty annotation labels for Open Land Use took 39.514240980148315s
Accuracy | Check White space in annotation for Open Land Use took 2.6726126670837402s
Accuracy | Check Datatype consistency for Open Land Use took 2.608842134475708s
Consistency | Disjoint class check for Open Land Use took 0.18088579177856445s
Consistency | Check Misplaced properties for Open Land Use took 99.3439564704895s
Consistency | Misplaced classes for Open Land Use took 8.423124313354492s
Consistency | Check Ontology hijacking for Open Land Use took 39.70940661430359s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.1980125904083252s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 86.4059910774231s
Conciseness | Check Extensional conciseness for Open Land Use took 2.740358591079712s
Conciseness | Check Intensional conciseness for Open Land Use took 0.5904765129089355s
Security | Sign check for Open Land Use took 0.7873008251190186s
Availability | Check URIs Dereferenciability for Open Land Use took 18.643495559692383s
Completeness | Calculation of interlinking completeness for Open Land Use took 1.5762841701507568s
Reputation | Calculation of the PageRank for Open Land Use took 0.0209810733795166s
Interlinking | Calculation of Degree of Connection for Open Land Use took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Land Use took 1.3113021850585938e-05s
INFO | --- Analysis for OLU took 2446.588193178177s
Availability | SPARQL endpoint availability check for OmegaWiki took 8.58306884765625e-05s
Availability | VoID file availability check for OmegaWiki took 0.0008404254913330078s
Completeness | Calculation of interlinking completeness for OmegaWiki took 131.06991958618164s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 4.220008850097656e-05s
Believability | Calculation of trust value for OmegaWiki took 1.7642974853515625e-05s
INFO | --- Analysis for omegawiki took 1048.739084482193s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.8085901737213135s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 131.04245853424072s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020952463150024414s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.000850677490234375s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.696846008300781e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 2.1219253540039062e-05s
INFO | --- Analysis for omwn-als took 789.0528032779694s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.23001718521118164s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 131.041246175766s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.021331787109375s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 3.361701965332031e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 9.441375732421875e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 2.8133392333984375e-05s
INFO | --- Analysis for omwn-arb took 787.91481757164s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.24404239654541016s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 131.0402569770813s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.03197979927062988s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 5.125999450683594e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 2.5987625122070312e-05s
INFO | --- Analysis for omwn-bul took 786.6900873184204s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.24979066848754883s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 131.05095601081848s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.021955490112304688s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.8835067749023438e-05s
INFO | --- Analysis for omwn-cow took 787.8283579349518s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.26467013359069824s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 131.04779076576233s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 4.649162292480469e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 2.1219253540039062e-05s
INFO | --- Analysis for omwn-cwn took 787.2657887935638s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.4625413417816162s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 131.04336142539978s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.021045684814453125s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 6.127357482910156e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 5.364418029785156e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.4543533325195312e-05s
INFO | --- Analysis for omwn-dan took 787.8557708263397s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.24723052978515625s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 131.05764961242676s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.021989822387695312s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.7404556274414062e-05s
INFO | --- Analysis for omwn-ell took 787.9700586795807s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.3176391124725342s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 131.04489302635193s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.022331714630126953s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0009779930114746094s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 5.1975250244140625e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-eng took 788.5740168094635s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.2717146873474121s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 131.04146647453308s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02662944793701172s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 4.649162292480469e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 2.2411346435546875e-05s
INFO | --- Analysis for omwn-fas took 788.3860685825348s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.269258975982666s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 131.04312586784363s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.021006345748901367s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.4543533325195312e-05s
INFO | --- Analysis for omwn-fin took 788.4877927303314s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.5794641971588135s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 131.04279685020447s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.792213439941406e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.5497207641601562e-05s
INFO | --- Analysis for omwn-fra took 788.2131106853485s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2572052478790283s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 131.0454568862915s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.021140575408935547s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0011131763458251953s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 5.555152893066406e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.8835067749023438e-05s
INFO | --- Analysis for omwn-heb took 788.8634016513824s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.25961899757385254s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 131.0412895679474s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.021032333374023438s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 4.792213439941406e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.430511474609375e-05s
INFO | --- Analysis for omwn-hrv took 787.7770884037018s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.23302197456359863s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 131.0534405708313s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.021553754806518555s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00010085105895996094s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 2.7418136596679688e-05s
INFO | --- Analysis for omwn-isl took 788.4721033573151s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.26496124267578125s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 131.04390954971313s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.632110595703125e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.5020370483398438e-05s
INFO | --- Analysis for omwn-ita took 788.1189465522766s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.5591325759887695s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 131.04379606246948s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.023136377334594727s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 4.458427429199219e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.8358230590820312e-05s
INFO | --- Analysis for omwn-iwn took 788.4423396587372s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.27154064178466797s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 131.0382857322693s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020786046981811523s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 4.9114227294921875e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.8835067749023438e-05s
INFO | --- Analysis for omwn-jpn took 788.3062784671783s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.24123549461364746s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 131.05594062805176s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020906448364257812s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.887580871582031e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 2.4080276489257812e-05s
INFO | --- Analysis for omwn-mcr took 788.8064522743225s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.25422024726867676s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 131.0501480102539s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.021338939666748047s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 4.863739013671875e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.6927719116210938e-05s
INFO | --- Analysis for omwn-msa took 788.3488147258759s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.29364752769470215s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 131.0417139530182s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02166914939880371s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 5.054473876953125e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 2.1696090698242188e-05s
INFO | --- Analysis for omwn-nld took 787.8907055854797s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.5338592529296875s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 131.05273246765137s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020948410034179688s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 5.078315734863281e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.71661376953125e-05s
INFO | --- Analysis for omwn-nor took 788.4553854465485s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2718691825866699s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 131.04762411117554s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 4.57763671875e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-pol took 788.1547198295593s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.28989434242248535s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 131.03984951972961s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.021831035614013672s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0009236335754394531s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 6.437301635742188e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 2.1457672119140625e-05s
INFO | --- Analysis for omwn-por took 787.9269104003906s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2642478942871094s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 131.03466987609863s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.02086782455444336s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0008206367492675781s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 9.632110595703125e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.8835067749023438e-05s
INFO | --- Analysis for omwn-ron took 789.1843640804291s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 1.387296438217163s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 131.0384500026703s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02231597900390625s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.553794860839844e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-slk took 529.0675532817841s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.25830650329589844s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2990407943725586s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-slv took 4.446059942245483s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.22816872596740723s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2741982936859131s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-swe took 3.44008207321167s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.2358841896057129s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2638108730316162s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-tha took 3.4675259590148926s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 5.284926176071167s
Availability | VoID file availability check for OntoBeef Domain took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.27166128158569336s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.410743713378906e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.3589859008789062e-05s
INFO | --- Analysis for ontobeef-domain took 32.14091753959656s
Availability | SPARQL endpoint availability check for Ontos News Portal took 7.462501525878906e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.7229011058807373s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.083747863769531e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.62939453125e-06s
INFO | --- Analysis for ontos-news-portal took 31.65660309791565s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.4345855712890625e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.7105917930603027s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020815610885620117s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 8.344650268554688e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.963992118835449s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.291534423828125e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.28882408142089844s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.100799560546875e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 7.62939453125e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.469286918640137s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 7.939338684082031e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2881278991699219s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.02010369300842285s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.8848648071289062e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 7.3909759521484375e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 3.0272018909454346s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 5.412101745605469e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.26319265365600586s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.029057979583740234s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.888938903808594e-05s
Believability | Calculation of trust value for Open Data Euskadi took 6.4373016357421875e-06s
INFO | --- Analysis for open-data-euskadi took 9.33490252494812s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.4345855712890625e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.26625847816467285s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010538101196289062s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.62939453125e-06s
INFO | --- Analysis for open-data-risp took 5.263912200927734s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.3461780548095703s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006556510925292969s
Extra | Recovery of all triples for Open Data Thesaurus took 1.684349536895752s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4999682903289795s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1259441375732422s
Interoperability | New terms check for Open Data Thesaurus took 1.3076047897338867s
Versatility | Languages check for Open Data Thesaurus took 0.14547348022460938s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.1243138313293457s
Security | Check HTTPS for Open Data Thesaurus took 0.3868265151977539s
Interpretability | RDF structures check for Open Data Thesaurus took 0.11336874961853027s
Versatility | Serialization formats check for Open Data Thesaurus took 0.12998437881469727s
Availability | RDF dump link check for Open Data Thesaurus took 1.235912561416626s
License | MR license check for Open Data Thesaurus took 0.12113547325134277s
License | HR license check for Open Data Thesaurus took 0.10584855079650879s
Amount of data | Number of property check for Open Data Thesaurus took 0.13617753982543945s
Understandability | Number of label check for Open Data Thesaurus took 0.11453533172607422s
Understandability | URI regex check for Open Data Thesaurus took 0.2088773250579834s
Understandability | Vocabs check for Open Data Thesaurus took 0.1456890106201172s
Verifiability | Authors check for Open Data Thesaurus took 0.12012004852294922s
Verifiability | Publishers check for Open Data Thesaurus took 0.15055131912231445s
Performance | Throughput check for Open Data Thesaurus took 10.484859228134155s
Amount of data | Check the number of entities for Open Data Thesaurus took 6.723403930664062e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.1284942626953125s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.1103973388671875s
Interlinking | skos check for Open Data Thesaurus took 0.12848520278930664s
Interlinking | skos check for Open Data Thesaurus took 0.09517121315002441s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.0966026782989502s
Currency | Creation date check for Open Data Thesaurus took 0.1875777244567871s
Currency | Modification date check for Open Data Thesaurus took 0.23620820045471191s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4628417491912842s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.14145755767822266s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.1205606460571289s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08934807777404785s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.20331978797912598s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011222362518310547s
Consistency | Disjoint class check for Open Data Thesaurus took 0.12107253074645996s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.21069121360778809s
Consistency | Misplaced classes for Open Data Thesaurus took 0.09715843200683594s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.39424467086792s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.277759075164795s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00014710426330566406s
Security | Sign check for Open Data Thesaurus took 0.09138035774230957s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.288848876953125s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.019769906997680664s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.677078247070312e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for open-data-thesaurus took 66.24489498138428s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.100799560546875e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.3070971965789795s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020107030868530273s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 8.106231689453125e-06s
INFO | --- Analysis for open-data-tor-vergata took 3.4982759952545166s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.124641418457031e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.26021528244018555s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.699562072753906e-05s
Believability | Calculation of trust value for Open Election Data Project took 6.198883056640625e-06s
INFO | --- Analysis for open-election-data-project took 3.8070147037506104s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.9305505752563477s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0010235309600830078s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.26834607124328613s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.916854858398438e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 5.7220458984375e-06s
INFO | --- Analysis for open-energy-info-wiki took 13.56143569946289s
Availability | SPARQL endpoint availability check for Open Library took 4.220008850097656e-05s
Availability | VoID file availability check for Open Library took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Open Library took 0.29581212997436523s
Reputation | Calculation of the PageRank for Open Library took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Open Library took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.651878356933594e-05s
Believability | Calculation of trust value for Open Library took 7.152557373046875e-06s
INFO | --- Analysis for open-library took 11.915160894393921s
Availability | SPARQL endpoint availability check for Open Directory took 3.981590270996094e-05s
Availability | VoID file availability check for Open Directory took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Open Directory took 0.24137043952941895s
Reputation | Calculation of the PageRank for Open Directory took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Directory took 8.344650268554688e-06s
INFO | --- Analysis for open_directory took 2.885551691055298s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.5109043121337891s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0002675056457519531s
Extra | Recovery of all triples for Open Land Use @PSNC took 122.40917134284973s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9580357074737549s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.22347354888916s
Interoperability | New terms check for Open Land Use @PSNC took 13.747303247451782s
Versatility | Languages check for Open Land Use @PSNC took 300.2378776073456s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 3.293060302734375s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.2327721118927002s
Versatility | Serialization formats check for Open Land Use @PSNC took 11.534526348114014s
Availability | RDF dump link check for Open Land Use @PSNC took 0.26050758361816406s
License | MR license check for Open Land Use @PSNC took 0.4105091094970703s
License | HR license check for Open Land Use @PSNC took 300.1754541397095s
Amount of data | Number of property check for Open Land Use @PSNC took 0.30280542373657227s
Understandability | Number of label check for Open Land Use @PSNC took 2.616420030593872s
Understandability | URI regex check for Open Land Use @PSNC took 0.7394912242889404s
Understandability | Vocabs check for Open Land Use @PSNC took 0.35517096519470215s
Verifiability | Authors check for Open Land Use @PSNC took 0.19912266731262207s
Verifiability | Publishers check for Open Land Use @PSNC took 0.23760104179382324s
Performance | Throughput check for Open Land Use @PSNC took 11.685346603393555s
Amount of data | Check the number of entities for Open Land Use @PSNC took 7.009506225585938e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.19802641868591309s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.20679616928100586s
Interlinking | skos check for Open Land Use @PSNC took 0.4727492332458496s
Interlinking | skos check for Open Land Use @PSNC took 0.4636819362640381s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 5.839865684509277s
Currency | Creation date check for Open Land Use @PSNC took 0.47915220260620117s
Currency | Modification date check for Open Land Use @PSNC took 0.22623252868652344s
Rep.Conc. | URIs length for Open Land Use @PSNC took 160.21627020835876s
Interoperability | New vocabularies check for Open Land Use @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.207688570022583s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.3003230094909668s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.28717851638793945s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 43.985145807266235s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6737589836120605s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.5948455333709717s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.19220829010009766s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 87.16125392913818s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.560920715332031s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 37.0014967918396s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.2166500091552734s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 92.91145491600037s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.794110059738159s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.671419620513916s
Security | Sign check for Open Land Use @PSNC took 0.4437878131866455s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 5.480019807815552s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 1.0776634216308594s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.021020889282226562s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 3.123283386230469e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 7.3909759521484375e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Open_Land_Use took 2281.2831525802612s
Availability | SPARQL endpoint availability check for flyatlas took 1.5000178813934326s
Availability | VoID file availability check for flyatlas took 0.00032210350036621094s
Completeness | Calculation of interlinking completeness for flyatlas took 0.7035455703735352s
Reputation | Calculation of the PageRank for flyatlas took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for flyatlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flyatlas took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.0040740966796875e-05s
Believability | Calculation of trust value for flyatlas took 7.62939453125e-06s
INFO | --- Analysis for openbiomed-flyatlas took 11.110183000564575s
Availability | SPARQL endpoint availability check for OpenCalais took 5.364418029785156e-05s
Availability | VoID file availability check for OpenCalais took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2602658271789551s
Reputation | Calculation of the PageRank for OpenCalais took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for OpenCalais took 8.249282836914062e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010585784912109375s
Believability | Calculation of trust value for OpenCalais took 8.106231689453125e-06s
INFO | --- Analysis for opencalais took 7.010865926742554s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.220008850097656e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.2850680351257324s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02015399932861328s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.271766662597656e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 5.7220458984375e-06s
INFO | --- Analysis for opencorporates took 4.192939519882202s
Availability | SPARQL endpoint availability check for OpenCyc took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenCyc took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2600395679473877s
Reputation | Calculation of the PageRank for OpenCyc took 0.02011394500732422s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.0001068115234375s
Believability | Calculation of trust value for OpenCyc took 7.152557373046875e-06s
INFO | --- Analysis for opencyc took 3.3304500579833984s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.27658939361572266s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.552436828613281e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 2.6196329593658447s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.28013110160827637s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.6283583641052246s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.26717448234558105s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.5762786865234375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.5390381813049316s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0003743171691894531s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2485649585723877s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.021311521530151367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0010073184967041016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 5.0067901611328125e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.3573548793792725s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2532801628112793s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.570850133895874s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.2515592575073242s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.02076578140258789s
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.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.4327259063720703s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0003726482391357422s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2773127555847168s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.475137948989868s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 7.557868957519531e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2876427173614502s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.021791458129882812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0008761882781982422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.4659781455993652s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2754549980163574s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.02027440071105957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007345676422119141s
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 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.5666441917419434s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.266279935836792s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.480468511581421s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2998378276824951s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.533996820449829s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.2835690975189209s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.555445432662964s
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.0005125999450683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.2814319133758545s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.9591064453125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.6656811237335205s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.26991987228393555s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02017068862915039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.443434000015259s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2643704414367676s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.53985595703125s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.28400182723999023s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020100116729736328s
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.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.5381128787994385s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.2968437671661377s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.676856517791748s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.26680970191955566s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.982948303222656e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.483839750289917s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.24553179740905762s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.326779842376709s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2584688663482666s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.5609097480773926s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 7.104873657226562e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0004062652587890625s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.2732682228088379s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.02019953727722168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.5763654708862305s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 5.340576171875e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2866201400756836s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.5938475131988525s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0005741119384765625s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.2619173526763916s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.686307191848755s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 6.29425048828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.2516019344329834s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.491518974304199s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.2928924560546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2787625789642334s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007729530334472656s
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 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.668008327484131s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.24790048599243164s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007774829864501953s
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 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.568834066390991s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.27323389053344727s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.839897155761719e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.6476423740386963s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2665517330169678s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.5464272499084473s
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.0005407333374023438s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.28044986724853516s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.02024221420288086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.6018450260162354s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.26574015617370605s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020058870315551758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007104873657226562s
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 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.5023560523986816s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2712841033935547s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020463943481445312s
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.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.5608508586883545s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007531642913818359s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.27339625358581543s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.02032780647277832s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.4881954193115234s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 5.507469177246094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.27620744705200195s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.544530153274536s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2689063549041748s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02116847038269043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.1021575927734375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.4287843704223633s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0005393028259277344s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.25763583183288574s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.4052255153656006s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2582104206085205s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 5.125999450683594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.5177395343780518s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.28194618225097656s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.568372964859009s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2580444812774658s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.4296061992645264s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 5.030632019042969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2833268642425537s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020169973373413086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.536311388015747s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2810235023498535s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.506111145019531e-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.5567407608032227s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.26728296279907227s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.6725165843963623s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.24980902671813965s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.5629756450653076s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2621583938598633s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020143747329711914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.5162434577941895s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 3.7940587997436523s
Availability | VoID file availability check for Open Data of Ecuador took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2750568389892578s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020209312438964844s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 9.036064147949219e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 7.152557373046875e-06s
INFO | --- Analysis for opendataec took 8.45755910873413s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.29182934761047363s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.1923611164093018s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.267692565917969e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.24531149864196777s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.512300491333008s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.124641418457031e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2814509868621826s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.943992853164673s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.863739013671875e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.252047061920166s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020355939865112305s
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.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.944758176803589s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.124641418457031e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.27834558486938477s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.955026626586914s
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.0004982948303222656s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2959747314453125s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.0150063037872314s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2653524875640869s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020130395889282227s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.933709144592285s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.696846008300781e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2575967311859131s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.971173048019409s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.124641418457031e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.2632324695587158s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.3758997917175293s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.41523003578186s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2436826229095459s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.361701965332031e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 7.867813110351562e-06s
INFO | --- Analysis for openlink-lod-cache took 62.87539458274841s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.124641418457031e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.3001058101654053s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.703636169433594e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 8.58306884765625e-06s
INFO | --- Analysis for openlinksw-dataspaces took 2.64233136177063s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 5.698204040527344e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.26633787155151367s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 0.00011110305786132812s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.245208740234375e-06s
INFO | --- Analysis for openlylocal took 6.075064659118652s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.8333203792572021s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2920565605163574s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02128744125366211s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0010066032409667969s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 8.726119995117188e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 7.3909759521484375e-06s
INFO | --- Analysis for openmobilenetwork took 3.5752060413360596s
Availability | SPARQL endpoint availability check for OpenTox took 4.00543212890625e-05s
Availability | VoID file availability check for OpenTox took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for OpenTox took 0.27800488471984863s
Reputation | Calculation of the PageRank for OpenTox took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.24249267578125e-05s
Believability | Calculation of trust value for OpenTox took 8.344650268554688e-06s
INFO | --- Analysis for opentox took 2.918178081512451s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 3.886222839355469e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.24256396293640137s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.314018249511719e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.867813110351562e-06s
INFO | --- Analysis for openuplabs took 2.85123610496521s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 5.173683166503906e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.249284029006958s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.023125410079956055s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 3.2901763916015625e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 8.344650268554688e-06s
INFO | --- Analysis for opus took 2.9692814350128174s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 3.9577484130859375e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2607572078704834s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0009076595306396484s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.743171691894531e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 7.867813110351562e-06s
INFO | --- Analysis for orcid took 3.0364151000976562s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.0785982608795166s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.25592947006225586s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020358800888061523s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.00012063980102539062s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.476714372634888s
Availability | SPARQL endpoint availability check for oreilly took 4.291534423828125e-05s
Availability | VoID file availability check for oreilly took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for oreilly took 0.26101255416870117s
Reputation | Calculation of the PageRank for oreilly took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for oreilly took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.982948303222656e-05s
Believability | Calculation of trust value for oreilly took 8.344650268554688e-06s
INFO | --- Analysis for oreilly took 5.074743986129761s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.407238483428955s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.26894593238830566s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.0517578125e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 8.106231689453125e-06s
INFO | --- Analysis for Organchem-Data took 7.286001205444336s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.06066584587097168s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2582101821899414s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020087718963623047s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.842613220214844e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for organic-edunet took 8.794477939605713s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.3776867389678955s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.00040841102600097656s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 13.239980459213257s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.8921205997467041s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.17283391952514648s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.526599645614624s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 9.620424747467041s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.14206767082214355s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.37548828125s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.15438199043273926s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.13841557502746582s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.15433526039123535s
License | HR license check for Open Research Knowledge Graph (ORKG) took 5.938273668289185s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.1452193260192871s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.1773521900177002s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.30354952812194824s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.13403725624084473s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.14774847030639648s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.16558098793029785s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.800640344619751s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.677078247070312e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.14648985862731934s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.15110182762145996s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16216373443603516s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.17244529724121094s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1490187644958496s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3313100337982178s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.32363367080688477s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 6.8490471839904785s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.1442105770111084s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.16216230392456055s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.16937565803527832s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 5.634459972381592s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.2687516212463379s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2705540657043457s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.24602222442626953s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.6688389778137207s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.8673086166381836s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 5.006759881973267s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.1968774795532227s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.127077579498291s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.29056644439697266s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.1486063003540039s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.14682292938232422s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2026.5342559814453s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 1.0744788646697998s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021538972854614258s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.9073486328125e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 1.6689300537109375e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 8.58306884765625e-06s
INFO | --- Analysis for orkg took 2315.4769310951233s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.215418577194214s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2854325771331787s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.021037817001342773s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 0.00010204315185546875s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 7.62939453125e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 32.582683086395264s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.6644253730773926s
Availability | VoID file availability check for OSM Semantic Network took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.29235243797302246s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.504753112792969e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.3909759521484375e-06s
INFO | --- Analysis for osm-semantic-network took 10.399446964263916s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.4571714401245117s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0002570152282714844s
Extra | Recovery of all triples for Open Transport Map @PSNC took 118.1317994594574s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.9630868434906006s
Amount of data | Number of triples check for Open Transport Map @PSNC took 8.931209564208984s
Interoperability | New terms check for Open Transport Map @PSNC took 15.369472026824951s
Versatility | Languages check for Open Transport Map @PSNC took 300.2456064224243s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 3.0543127059936523s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.26581430435180664s
Versatility | Serialization formats check for Open Transport Map @PSNC took 9.967979907989502s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.30585408210754395s
License | MR license check for Open Transport Map @PSNC took 0.5728209018707275s
License | HR license check for Open Transport Map @PSNC took 300.23858666419983s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.2832610607147217s
Understandability | Number of label check for Open Transport Map @PSNC took 2.2950830459594727s
Understandability | URI regex check for Open Transport Map @PSNC took 0.5965380668640137s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.315352201461792s
Verifiability | Authors check for Open Transport Map @PSNC took 0.20012187957763672s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.25382280349731445s
Performance | Throughput check for Open Transport Map @PSNC took 11.420247316360474s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 8.153915405273438e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.18682265281677246s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.21291589736938477s
Interlinking | skos check for Open Transport Map @PSNC took 0.45234227180480957s
Interlinking | skos check for Open Transport Map @PSNC took 0.48059797286987305s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 4.58757758140564s
Currency | Creation date check for Open Transport Map @PSNC took 0.4846794605255127s
Currency | Modification date check for Open Transport Map @PSNC took 0.24190568923950195s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 170.0209836959839s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.20205354690551758s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.3293325901031494s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.32146596908569336s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 43.98147964477539s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.663379669189453s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.5950257778167725s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.18553924560546875s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 89.91036987304688s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.268336057662964s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 37.93981981277466s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.253607988357544s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 84.34692597389221s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.7847492694854736s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.6266829967498779s
Security | Sign check for Open Transport Map @PSNC took 0.5723869800567627s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 5.1007843017578125s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.9681398868560791s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for OTM took 2298.3065428733826s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 3.981590270996094e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.7110817432403564s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.152557373046875e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 6.090536117553711s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.124641418457031e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.7089922428131104s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 4.3018128871917725s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 3.910064697265625e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.2503387928009033s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 4.2514214515686035s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.076957702636719e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.28286242485046387s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.02033400535583496s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.8371810913085938e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.62939453125e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 2.9784605503082275s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 3.8623809814453125e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.7045943737030029s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020129680633544922s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.765655517578125e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 7.62939453125e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 3.3654849529266357s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 3.910064697265625e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.23413467407226562s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 3.3348183631896973s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.100799560546875e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0003314018249511719s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2777578830718994s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 2.8371810913085938e-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 3.008096933364868s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 3.910064697265625e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2823803424835205s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 6.4373016357421875e-06s
INFO | --- Analysis for oxpoints took 2.877957820892334s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.797039270401001s
Availability | VoID file availability check for Pali English Lexicon took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.2709996700286865s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.7894973754882812e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.3909759521484375e-06s
INFO | --- Analysis for pali-english-lexicon took 6.991761922836304s
Availability | SPARQL endpoint availability check for PanLex took 0.39462876319885254s
Availability | VoID file availability check for PanLex took 0.0003504753112792969s
Completeness | Calculation of interlinking completeness for PanLex took 0.2893855571746826s
Reputation | Calculation of the PageRank for PanLex took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for PanLex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.033348083496094e-05s
Believability | Calculation of trust value for PanLex took 7.3909759521484375e-06s
INFO | --- Analysis for panlex took 2.829103946685791s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.863739013671875e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.257735013961792s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020718812942504883s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 4.38690185546875e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 8.344650268554688e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.618829965591431s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.07480764389038086s
Availability | VoID file availability check for patents.data.gov.uk took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.27356481552124023s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.8160552978515625e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.5112578868865967s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.124641418457031e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.00033211708068847656s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.2733311653137207s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.528594970703125e-05s
Believability | Calculation of trust value for PDEV-Lemon took 9.059906005859375e-06s
INFO | --- Analysis for pdev-lemon took 3.9681034088134766s
Availability | SPARQL endpoint availability check for pdevlemon took 5.245208740234375e-05s
Availability | VoID file availability check for pdevlemon took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.25866007804870605s
Reputation | Calculation of the PageRank for pdevlemon took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for pdevlemon took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.8133392333984375e-05s
Believability | Calculation of trust value for pdevlemon took 6.9141387939453125e-06s
INFO | --- Analysis for pdevlemon took 3.1208720207214355s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.1484832763671875e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008678436279296875s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2748696804046631s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.130073547363281e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 8.344650268554688e-06s
INFO | --- Analysis for periodo took 18.69108819961548s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.172325134277344e-05s
Availability | VoID file availability check for Personal_Homepages took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2691514492034912s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00038504600524902344s
Believability | Calculation of trust value for Personal_Homepages took 8.821487426757812e-06s
INFO | --- Analysis for personal-homepages took 2.366816282272339s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology of University People took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2832019329071045s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020586490631103516s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.0994415283203125e-05s
Believability | Calculation of trust value for Ontology of University People took 8.106231689453125e-06s
INFO | --- Analysis for PersonOnto took 2.445209264755249s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.332914590835571s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2661733627319336s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1444091796875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.152557373046875e-06s
INFO | --- Analysis for PFKHS took 12.741533279418945s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.5401880741119385s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2611720561981201s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02066636085510254s
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.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1920928955078125e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 8.821487426757812e-06s
INFO | --- Analysis for PFRPPH took 9.67142939567566s
Availability | SPARQL endpoint availability check for PGxLOD took 0.4849710464477539s
Availability | VoID file availability check for PGxLOD took 0.0005867481231689453s
Extra | Recovery of all triples for PGxLOD took 2.346656560897827s
Performance | Total latancy measurement for PGxLOD took 0.8241395950317383s
Amount of data | Number of triples check for PGxLOD took 0.7784202098846436s
Interoperability | New terms check for PGxLOD took 1.9522600173950195s
Versatility | Languages check for PGxLOD took 60.25864386558533s
Interpretability | Number of blank nodes check for PGxLOD took 1.476574420928955s
Interpretability | RDF structures check for PGxLOD took 0.5380218029022217s
Versatility | Serialization formats check for PGxLOD took 0.36700892448425293s
Availability | RDF dump link check for PGxLOD took 53.608506202697754s
License | MR license check for PGxLOD took 0.8487615585327148s
License | HR license check for PGxLOD took 63.74589967727661s
Amount of data | Number of property check for PGxLOD took 0.1757960319519043s
Understandability | Number of label check for PGxLOD took 2.7971155643463135s
Understandability | URI regex check for PGxLOD took 0.4379279613494873s
Understandability | Vocabs check for PGxLOD took 0.37323594093322754s
Verifiability | Authors check for PGxLOD took 0.37872743606567383s
Verifiability | Publishers check for PGxLOD took 0.329082727432251s
Performance | Throughput check for PGxLOD took 10.622995853424072s
Amount of data | Check the number of entities for PGxLOD took 0.12991571426391602s
Verifiability | Contribs. check for PGxLOD took 0.1714036464691162s
Interlinking | sameAs chians check for PGxLOD took 0.2569713592529297s
Interlinking | skos check for PGxLOD took 1.7998199462890625s
Interlinking | skos check for PGxLOD took 0.20117616653442383s
Timeliness | dataset update frequency check for PGxLOD took 0.38550662994384766s
Currency | Creation date check for PGxLOD took 0.564276933670044s
Currency | Modification date check for PGxLOD took 0.3702883720397949s
Rep.Conc. | URIs length for PGxLOD took 6.712831020355225s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.16392064094543457s
Accuracy | Check Functional Property for PGxLOD took 0.22036099433898926s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.20772409439086914s
Accuracy | Check Empty annotation labels for PGxLOD took 1.2254688739776611s
Accuracy | Check White space in annotation for PGxLOD took 0.03737211227416992s
Accuracy | Check Datatype consistency for PGxLOD took 0.027559518814086914s
Consistency | Disjoint class check for PGxLOD took 0.3209826946258545s
Consistency | Check Misplaced properties for PGxLOD took 6.645911931991577s
Consistency | Misplaced classes for PGxLOD took 0.3169713020324707s
Consistency | Check Ontology hijacking for PGxLOD took 1.9426965713500977s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.1346256732940674s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.05359411239624s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03317070007324219s
Conciseness | Check Intensional conciseness for PGxLOD took 0.2589256763458252s
Security | Sign check for PGxLOD took 0.19478607177734375s
Availability | Check URIs Dereferenciability for PGxLOD took 23648.215434789658s
Completeness | Calculation of interlinking completeness for PGxLOD took 1.6632137298583984s
Reputation | Calculation of the PageRank for PGxLOD took 0.022988319396972656s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 0.0001277923583984375s
Believability | Calculation of trust value for PGxLOD took 8.58306884765625e-06s
INFO | --- Analysis for PGxLOD took 222555.82310652733s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.3279767036437988s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.7078280448913574s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.910064697265625e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 8.58306884765625e-06s
INFO | --- Analysis for phoible took 7.708622694015503s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.267692565917969e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.2939338684082031s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.020127534866333008s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.9087066650390625e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 7.62939453125e-06s
INFO | --- Analysis for PISM took 20.07490038871765s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.4345855712890625e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00054931640625s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.29418063163757324s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020345449447631836s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.20159912109375e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.62939453125e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.5479981899261475s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.3561711311340332s
Availability | VoID file availability check for digitized plant specimen took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.25441503524780273s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.818771362304688e-05s
Believability | Calculation of trust value for digitized plant specimen took 8.106231689453125e-06s
INFO | --- Analysis for plant-specimen took 4.109125375747681s
Availability | SPARQL endpoint availability check for Pleiades took 7.343292236328125e-05s
Availability | VoID file availability check for Pleiades took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Pleiades took 0.25611305236816406s
Reputation | Calculation of the PageRank for Pleiades took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.20159912109375e-05s
Believability | Calculation of trust value for Pleiades took 7.62939453125e-06s
INFO | --- Analysis for pleiades took 14.251290559768677s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 6.103515625e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.27579450607299805s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020824909210205078s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.170967102050781e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.3909759521484375e-06s
INFO | --- Analysis for podorozhnyk took 23.38626456260681s
Availability | SPARQL endpoint availability check for Poképédia took 4.76837158203125e-05s
Availability | VoID file availability check for Poképédia took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Poképédia took 0.26753807067871094s
Reputation | Calculation of the PageRank for Poképédia took 0.02079606056213379s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.128715515136719e-05s
Believability | Calculation of trust value for Poképédia took 6.9141387939453125e-06s
INFO | --- Analysis for pokepedia-fr took 3.103496789932251s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.1484832763671875e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.28079938888549805s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.534027099609375e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 6.198883056640625e-06s
INFO | --- Analysis for polymath-virtual-library took 5.596310377120972s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.672658920288086s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2902541160583496s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2874603271484375e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.9141387939453125e-06s
INFO | --- Analysis for portuguese_prisons_releases took 6.893059968948364s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.00543212890625e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.27732014656066895s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.147125244140625e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 3.0285887718200684s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.220008850097656e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.26466965675354004s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.123283386230469e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 9.059906005859375e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.944373607635498s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 3.981590270996094e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.26935672760009766s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 3.0994415283203125e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 8.821487426757812e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 3.404324769973755s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 3.933906555175781e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2576487064361572s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.147125244140625e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 8.106231689453125e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.911691904067993s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.410743713378906e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.26934146881103516s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0008380413055419922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.361701965332031e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.944504737854004s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 7.867813110351562e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.24512052536010742s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020388126373291016s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.8329107761383057s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 8.0108642578125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.26634979248046875s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.361701965332031e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.8875486850738525s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 3.9577484130859375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.26937031745910645s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020141124725341797s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.790855407714844e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.8699982166290283s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.275188684463501s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020334720611572266s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 3.006619453430176s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 5.1975250244140625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.268312931060791s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.02089524269104004s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0009417533874511719s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.552436828613281e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.991367816925049s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 3.981590270996094e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.26205992698669434s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.02137446403503418s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.9404404163360596s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 3.981590270996094e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.2768399715423584s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0009024143218994141s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.24249267578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 3.005786180496216s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 3.933906555175781e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2598433494567871s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.86102294921875e-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.9743800163269043s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.0531158447265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2625997066497803s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.974743127822876s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 3.8623809814453125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2770516872406006s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.904529571533203s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.4345855712890625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2731325626373291s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.504753112792969e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 6.198883056640625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.928189992904663s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 3.933906555175781e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.26232481002807617s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020009994506835938s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 6.198883056640625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.9016165733337402s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.0531158447265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2730062007904053s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.020131349563598633s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.9325485229492188e-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.957979917526245s
Availability | SPARQL endpoint availability check for prefix.cc took 4.076957702636719e-05s
Availability | VoID file availability check for prefix.cc took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2669205665588379s
Reputation | Calculation of the PageRank for prefix.cc took 0.02005791664123535s
Interlinking | Calculation of Degree of Connection for prefix.cc took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for prefix.cc took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.4809112548828125e-05s
Believability | Calculation of trust value for prefix.cc took 6.9141387939453125e-06s
INFO | --- Analysis for prefix-cc took 3.284843921661377s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.9777395725250244s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.26058149337768555s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.673004150390625e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 5.9604644775390625e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 8.124488115310669s
Availability | SPARQL endpoint availability check for PreLex took 4.4175519943237305s
Availability | VoID file availability check for PreLex took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for PreLex took 0.3763854503631592s
Reputation | Calculation of the PageRank for PreLex took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for PreLex took 8.344650268554688e-05s
Believability | Calculation of trust value for PreLex took 7.867813110351562e-06s
INFO | --- Analysis for prelex took 192.4823169708252s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.400465965270996s
Availability | VoID file availability check for Prelinger Archives took 0.0007789134979248047s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.2695889472961426s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020886898040771484s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.075599670410156e-05s
Believability | Calculation of trust value for Prelinger Archives took 8.106231689453125e-06s
INFO | --- Analysis for prelinger_archives took 11.440621852874756s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.8231165409088135s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0005908012390136719s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 4.814439535140991s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 1.3173556327819824s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.4783976078033447s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 2.0645501613616943s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 58.87377691268921s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.08130145072937012s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.07351136207580566s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.08196353912353516s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.12215995788574219s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.08130979537963867s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.09072470664978027s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 0.897341251373291s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.1203165054321289s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 0.082275390625s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.16835474967956543s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.08287382125854492s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.08884358406066895s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.08759284019470215s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 10.461732149124146s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 7.128715515136719e-05s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.08894777297973633s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.08066463470458984s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.08808422088623047s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.08556389808654785s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.09136557579040527s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 0.20110464096069336s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.20458006858825684s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 3.7627506256103516s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.11090445518493652s
Accuracy | Check Functional Property for PreMOn (Predicate Model for Ontologies) took 0.10931277275085449s
Accuracy | Check Inverse Functional Property for PreMOn (Predicate Model for Ontologies) took 0.08495450019836426s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 1.0804693698883057s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08280467987060547s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.08139753341674805s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.1154325008392334s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 1.7377538681030273s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 0.37317609786987305s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.2761752605438232s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.1687428951263428s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 2.8090553283691406s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.09153628349304199s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.11360025405883789s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.048623085021972656s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 876.7457265853882s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.41774988174438477s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.02138996124267578s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 7.700920104980469e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 1.6689300537109375e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 8.106231689453125e-06s
INFO | --- Analysis for premon took 993.8624353408813s
Availability | SPARQL endpoint availability check for Previsible took 4.100799560546875e-05s
Availability | VoID file availability check for Previsible took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Previsible took 0.2784590721130371s
Reputation | Calculation of the PageRank for Previsible took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for Previsible took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.1205673217773438e-05s
Believability | Calculation of trust value for Previsible took 7.62939453125e-06s
INFO | --- Analysis for Previsible took 3.2904412746429443s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.0531158447265625e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.6694860458374023s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02023792266845703s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.7697296142578125e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 7.3909759521484375e-06s
INFO | --- Analysis for princeton-library-findingaids took 7.70059871673584s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.5338764190673828s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.27301764488220215s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.02020263671875s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.528594970703125e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for PrinParLat took 4.587854623794556s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.553037166595459s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.6818497180938721s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.772445678710938e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.0251998901367188e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 3.6787362098693848s
Availability | SPARQL endpoint availability check for Prior Panel took 7.987022399902344e-05s
Availability | VoID file availability check for Prior Panel took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.27591681480407715s
Reputation | Calculation of the PageRank for Prior Panel took 0.020151853561401367s
Interlinking | Calculation of Degree of Connection for Prior Panel took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.075599670410156e-05s
Believability | Calculation of trust value for Prior Panel took 7.3909759521484375e-06s
INFO | --- Analysis for Prior_Panel took 2.404691696166992s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.100799560546875e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.2732689380645752s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 2.9802322387695312e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 8.344650268554688e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.914370059967041s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 3.9577484130859375e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.27640295028686523s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 2.9802322387695312e-05s
Believability | Calculation of trust value for Procomún SPARQL took 7.62939453125e-06s
INFO | --- Analysis for procomun-sparql took 3.385298728942871s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.9114227294921875e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.27126264572143555s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 2.6464462280273438e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 8.106231689453125e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.9932844638824463s
Availability | SPARQL endpoint availability check for ProductDB took 20.56655216217041s
Availability | VoID file availability check for ProductDB took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for ProductDB took 0.7354223728179932s
Reputation | Calculation of the PageRank for ProductDB took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for ProductDB took 8.58306884765625e-05s
Believability | Calculation of trust value for ProductDB took 8.344650268554688e-06s
INFO | --- Analysis for productdb took 103.27731609344482s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.745901346206665s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.43865966796875e-05s
Believability | Calculation of trust value for Product Types Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for productontology took 5.267660617828369s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.076957702636719e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.30626392364501953s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02047419548034668s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010228157043457031s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 5.794501066207886s
Availability | SPARQL endpoint availability check for provenanceweb took 0.0546267032623291s
Availability | VoID file availability check for provenanceweb took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.28613829612731934s
Reputation | Calculation of the PageRank for provenanceweb took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.177757263183594e-05s
Believability | Calculation of trust value for provenanceweb took 8.106231689453125e-06s
INFO | --- Analysis for provenanceweb took 49.57890224456787s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.1961669921875e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.25304412841796875s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.02045583724975586s
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.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010061264038085938s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 8.106231689453125e-06s
INFO | --- Analysis for proyectoapadrina took 4.925007343292236s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 26.856457233428955s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0010344982147216797s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.29587697982788086s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02110147476196289s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 4.2438507080078125e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 6.4373016357421875e-06s
INFO | --- Analysis for pscs-catalogue took 126.18057322502136s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.3392181396484375e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2689361572265625s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.028240680694580078s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0010440349578857422s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 0.00010728836059570312s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 9.059906005859375e-06s
INFO | --- Analysis for psh-subject-headings took 3.6548259258270264s
Availability | SPARQL endpoint availability check for Depression took 0.4147460460662842s
Availability | VoID file availability check for Depression took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Depression took 0.2707245349884033s
Reputation | Calculation of the PageRank for Depression took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Depression took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Depression took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Depression took 2.8848648071289062e-05s
Believability | Calculation of trust value for Depression took 8.106231689453125e-06s
INFO | --- Analysis for Psychology took 3.2248141765594482s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.076957702636719e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.28386950492858887s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.482269287109375e-05s
Believability | Calculation of trust value for PubChem RDF took 7.3909759521484375e-06s
INFO | --- Analysis for PubChem_RDF took 4.900742053985596s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 3.886222839355469e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2615361213684082s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020726919174194336s
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.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.0279159545898438e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 6.67572021484375e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 3.3519277572631836s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 1.4622447490692139s
Availability | VoID file availability check for Public Spending in Greece took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.29813575744628906s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0009150505065917969s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 9.036064147949219e-05s
Believability | Calculation of trust value for Public Spending in Greece took 2.3603439331054688e-05s
INFO | --- Analysis for public-spending-in-greece took 9.079834222793579s
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.0002532005310058594s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.2787821292877197s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020169734954833984s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.8848648071289062e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 1.0013580322265625e-05s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.908078193664551s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.37265586853027344s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006506443023681641s
Extra | Recovery of all triples for Publications Office Authority tables took 115.25725626945496s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5769779682159424s
Amount of data | Number of triples check for Publications Office Authority tables took 87.51323175430298s
Interoperability | New terms check for Publications Office Authority tables took 116.53585410118103s
Versatility | Languages check for Publications Office Authority tables took 300.18911719322205s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 1.6747074127197266s
Security | Check HTTPS for Publications Office Authority tables took 0.30483412742614746s
Interpretability | RDF structures check for Publications Office Authority tables took 0.6469666957855225s
Versatility | Serialization formats check for Publications Office Authority tables took 4.782423734664917s
Availability | RDF dump link check for Publications Office Authority tables took 0.2214527130126953s
License | MR license check for Publications Office Authority tables took 0.3310117721557617s
License | HR license check for Publications Office Authority tables took 300.1048970222473s
Amount of data | Number of property check for Publications Office Authority tables took 0.16617488861083984s
Understandability | Number of label check for Publications Office Authority tables took 7.49048638343811s
Understandability | URI regex check for Publications Office Authority tables took 0.4373295307159424s
Understandability | Vocabs check for Publications Office Authority tables took 0.12114262580871582s
Verifiability | Authors check for Publications Office Authority tables took 0.3155510425567627s
Verifiability | Publishers check for Publications Office Authority tables took 0.2566366195678711s
Performance | Throughput check for Publications Office Authority tables took 10.403461217880249s
Amount of data | Check the number of entities for Publications Office Authority tables took 0.00010752677917480469s
Verifiability | Contribs. check for Publications Office Authority tables took 0.19296765327453613s
Interlinking | sameAs chians check for Publications Office Authority tables took 11.801336288452148s
Interlinking | skos check for Publications Office Authority tables took 0.5398879051208496s
Interlinking | skos check for Publications Office Authority tables took 0.5377390384674072s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.24833941459655762s
Currency | Creation date check for Publications Office Authority tables took 0.49772024154663086s
Currency | Modification date check for Publications Office Authority tables took 0.27231550216674805s
Rep.Conc. | URIs length for Publications Office Authority tables took 571.016405582428s
Interoperability | New vocabularies check for Publications Office Authority tables took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.17516088485717773s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.12130308151245117s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.1763772964477539s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 32.323960304260254s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.1081528663635254s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.5948257446289062s
Consistency | Disjoint class check for Publications Office Authority tables took 0.1873462200164795s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.43339347839355s
Consistency | Misplaced classes for Publications Office Authority tables took 9.183479070663452s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 35.17556834220886s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 12.327498197555542s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.30540704727173s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.0907392501831055s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.6101300716400146s
Security | Sign check for Publications Office Authority tables took 0.19401335716247559s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 4.119175672531128s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.615689754486084s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.05319833755493164s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.6689300537109375e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 5.4836273193359375e-06s
INFO | --- Analysis for publications_office_authority_tables took 15605.593722105026s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.1484832763671875e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.2694132328033447s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.02136683464050293s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.4809112548828125e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 7.867813110351562e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 5.174949645996094s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.267692565917969e-05s
Availability | VoID file availability check for QBOAirbase took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.696324348449707s
Reputation | Calculation of the PageRank for QBOAirbase took 0.0285799503326416s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0014035701751708984s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 0.00011444091796875s
Believability | Calculation of trust value for QBOAirbase took 8.344650268554688e-06s
INFO | --- Analysis for qboairbase took 138.74476432800293s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.100799560546875e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.27287936210632324s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.9325485229492188e-05s
Believability | Calculation of trust value for qualitywebdata.org took 9.298324584960938e-06s
INFO | --- Analysis for qualitywebdata-org took 4.7743308544158936s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.220008850097656e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.26377177238464355s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.765655517578125e-05s
Believability | Calculation of trust value for Qualité de l'air took 7.152557373046875e-06s
INFO | --- Analysis for Qualité_de_l'air took 3.3177144527435303s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.982948303222656e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.2811088562011719s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.020331621170043945s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.552436828613281e-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 49.78511095046997s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5900511741638184s
Availability | VoID file availability check for Querolus in LiLa took 0.0004165172576904297s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.2616307735443115s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.457069396972656e-05s
Believability | Calculation of trust value for Querolus in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for Querolus took 4.3124635219573975s
Availability | SPARQL endpoint availability check for Quotations Book took 4.220008850097656e-05s
Availability | VoID file availability check for Quotations Book took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.27970170974731445s
Reputation | Calculation of the PageRank for Quotations Book took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.170967102050781e-05s
Believability | Calculation of trust value for Quotations Book took 8.344650268554688e-06s
INFO | --- Analysis for quotations_book took 3.3716604709625244s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.25780439376831055s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 8.821487426757812e-06s
INFO | --- Analysis for r4r took 2.9193897247314453s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.9254601001739502s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2868499755859375s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.02014470100402832s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.673004150390625e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.62939453125e-06s
INFO | --- Analysis for racai-legalnero took 5.389158248901367s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.38690185546875e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.2894158363342285s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.504753112792969e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 8.344650268554688e-06s
INFO | --- Analysis for racai-llod-corola-we took 2.945744037628174s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 2.1216249465942383s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.28507304191589355s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.123283386230469e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 8.821487426757812e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 5.148617506027222s
Availability | SPARQL endpoint availability check for RoLEX took 1.8795905113220215s
Availability | VoID file availability check for RoLEX took 0.0003304481506347656s
Completeness | Calculation of interlinking completeness for RoLEX took 0.2958807945251465s
Reputation | Calculation of the PageRank for RoLEX took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0009019374847412109s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.409385681152344e-05s
Believability | Calculation of trust value for RoLEX took 8.821487426757812e-06s
INFO | --- Analysis for racai-llod-rolex took 4.893357038497925s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.27319884300231934s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.0994415283203125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.620422840118408s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.315376281738281e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.2640821933746338s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.790855407714844e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 8.344650268554688e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.6482365131378174s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.100799560546875e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.26238369941711426s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.024136066436767578s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.0279159545898438e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.5972299575805664s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.2438507080078125e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.25290560722351074s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.504753112792969e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.7386419773101807s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.4681437015533447s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.2743840217590332s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 2.956390380859375e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-rtasc took 3.995303153991699s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.464827299118042s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.29677605628967285s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0009648799896240234s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 3.504753112792969e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-simonero took 3.5083365440368652s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.19894075393676758s
Availability | VoID file availability check for Rådata nå! took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2664458751678467s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0009143352508544922s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 9.1552734375e-05s
Believability | Calculation of trust value for Rådata nå! took 7.62939453125e-06s
INFO | --- Analysis for radatana took 4.689798593521118s
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.0004248619079589844s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.2944011688232422s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.030742168426513672s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0013570785522460938s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 5.435943603515625e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 8.106231689453125e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 16.20790672302246s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.172325134277344e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0003566741943359375s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.280703067779541s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.0279159545898438e-05s
Believability | Calculation of trust value for Raphael Research Resource took 6.9141387939453125e-06s
INFO | --- Analysis for raphaelresearchresource took 2.890970230102539s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.851444005966187s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.3398427963256836s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.147125244140625e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 7.867813110351562e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 27.30432939529419s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 391.7130386829376s
Availability | VoID file availability check for Polish LGU financial statements took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.2476346492767334s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 4.601478576660156e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 7.3909759521484375e-06s
INFO | --- Analysis for Rb_PL_LGU took 666.6558773517609s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.673004150390625e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.2753758430480957s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 6.04824423789978s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 3.981590270996094e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.28650474548339844s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 4.214882850646973s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.2601170539855957s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.02030038833618164s
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.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 2.8133392333984375e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 2.8692471981048584s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.26704955101013184s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.337860107421875e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.960904598236084s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 7.224082946777344e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.27460503578186035s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.0279159545898438e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 7.152557373046875e-06s
INFO | --- Analysis for rcahmw-periods-list took 3.3681259155273438s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.315376281738281e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.27181243896484375s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.344650268554688e-05s
Believability | Calculation of trust value for RDF Book Mashup took 8.344650268554688e-06s
INFO | --- Analysis for rdf-book-mashup took 3.4213569164276123s
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.00048732757568359375s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2891201972961426s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020973682403564453s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010895729064941406s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 8.344650268554688e-06s
INFO | --- Analysis for rdfize-lastfm took 2.6238677501678467s
Availability | SPARQL endpoint availability check for RDFLicense took 261.62363505363464s
Availability | VoID file availability check for RDFLicense took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.7542171478271484s
Reputation | Calculation of the PageRank for RDFLicense took 0.02087116241455078s
Interlinking | Calculation of Degree of Connection for RDFLicense took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 4.315376281738281e-05s
Believability | Calculation of trust value for RDFLicense took 7.62939453125e-06s
INFO | --- Analysis for rdflicense took 538.6319646835327s
Availability | SPARQL endpoint availability check for RDFohloh took 4.267692565917969e-05s
Availability | VoID file availability check for RDFohloh took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.7687726020812988s
Reputation | Calculation of the PageRank for RDFohloh took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for RDFohloh took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 8.702278137207031e-05s
Believability | Calculation of trust value for RDFohloh took 8.58306884765625e-06s
INFO | --- Analysis for rdfohloh took 9.015504360198975s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.74446702003479s
Availability | VoID file availability check for Reactome RDF took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2501697540283203s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.457069396972656e-05s
Believability | Calculation of trust value for Reactome RDF took 7.62939453125e-06s
INFO | --- Analysis for reactome-rdf took 4.237355947494507s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 3.559682607650757s
Availability | VoID file availability check for Rechtspraak.nl took 0.0011913776397705078s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.27317285537719727s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.036064147949219e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 5.9604644775390625e-06s
INFO | --- Analysis for rechtspraak took 9.97927188873291s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.172325134277344e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2608795166015625s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.344650268554688e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 7.152557373046875e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 9.422293901443481s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.09327912330627441s
Availability | VoID file availability check for reference.data.gov.uk took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2619442939758301s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020194292068481445s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001461505889892578s
Believability | Calculation of trust value for reference.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.6432855129241943s
Availability | SPARQL endpoint availability check for Regiony took 4.506111145019531e-05s
Availability | VoID file availability check for Regiony took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Regiony took 0.2756068706512451s
Reputation | Calculation of the PageRank for Regiony took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for Regiony took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.2901763916015625e-05s
Believability | Calculation of trust value for Regiony took 8.106231689453125e-06s
INFO | --- Analysis for regiony took 2.882577657699585s
Availability | SPARQL endpoint availability check for RELD took 261.69444251060486s
Availability | VoID file availability check for RELD took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for RELD took 0.3126943111419678s
Reputation | Calculation of the PageRank for RELD took 0.02114081382751465s
Interlinking | Calculation of Degree of Connection for RELD took 1.52587890625e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for RELD took 3.24249267578125e-05s
Believability | Calculation of trust value for RELD took 8.821487426757812e-06s
INFO | --- Analysis for RELD took 536.347110748291s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.1921064853668213s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.00054931640625s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.473905086517334s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.4804191589355469s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.920013666152954s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.624133825302124s
Versatility | Languages check for Repository for Linked Open Archival Data took 9.560810565948486s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 1.8874340057373047s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.23575663566589355s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.2443068027496338s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.28578805923461914s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.15507936477661133s
License | MR license check for Repository for Linked Open Archival Data took 0.31116652488708496s
License | HR license check for Repository for Linked Open Archival Data took 10.497207403182983s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.11399626731872559s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.9243428707122803s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.3931293487548828s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.11223244667053223s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.16116786003112793s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.16878938674926758s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.275510549545288s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.00011205673217773438s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.12113285064697266s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.11565661430358887s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.25219011306762695s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.06526637077331543s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.2526669502258301s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.15227055549621582s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.1622300148010254s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 3.922072649002075s
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.08228778839111328s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.09430885314941406s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.06463408470153809s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.4205923080444336s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.028504610061645508s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.029315948486328125s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.22211623191833496s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.90199875831604s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.19289612770080566s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.6212635040283203s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.1894011497497559s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.8162031173706055s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.03061842918395996s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.1529393196105957s
Security | Sign check for Repository for Linked Open Archival Data took 0.5036220550537109s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 2304.0667424201965s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 1.6538877487182617s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02171611785888672s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007181167602539062s
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 9.5367431640625e-06s
INFO | --- Analysis for reload took 2429.3954141139984s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.673004150390625e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.27107834815979004s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.3855438232421875e-05s
Believability | Calculation of trust value for Land use merced dataset took 6.9141387939453125e-06s
INFO | --- Analysis for remote_Sensing took 13.280776262283325s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.8569707870483398s
Availability | VoID file availability check for Renewable Energy Generators took 0.0008170604705810547s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.70448899269104s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.5299530029296875e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 5.0067901611328125e-06s
INFO | --- Analysis for renewable_energy_generators took 11.606191635131836s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.1009666919708252s
Availability | VoID file availability check for research.data.gov.uk took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.2621912956237793s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 8.916854858398438e-05s
Believability | Calculation of trust value for research.data.gov.uk took 7.62939453125e-06s
INFO | --- Analysis for research-data-gov-uk took 3.068074941635132s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.00543212890625e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.3306698799133301s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 2.9325485229492188e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 7.3909759521484375e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 3.0819268226623535s
Availability | SPARQL endpoint availability check for Restaurantes took 4.076957702636719e-05s
Availability | VoID file availability check for Restaurantes took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.25568199157714844s
Reputation | Calculation of the PageRank for Restaurantes took 0.03090381622314453s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0014531612396240234s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.981590270996094e-05s
Believability | Calculation of trust value for Restaurantes took 7.62939453125e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.954241991043091s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.172325134277344e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.2829294204711914s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.413459777832031e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 9.059906005859375e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.2055346965789795s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.05277276039123535s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.25925517082214355s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.218650817871094e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 6.4373016357421875e-06s
INFO | --- Analysis for revistas_turismo took 2.4087259769439697s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2838928699493408s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2709846496582031s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.02096414566040039s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011682510375976562s
Believability | Calculation of trust value for Revyu.com - Review Anything took 7.62939453125e-06s
INFO | --- Analysis for revyu took 2.6969850063323975s
Availability | SPARQL endpoint availability check for sdafsadf took 0.36049389839172363s
Availability | VoID file availability check for sdafsadf took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.2533853054046631s
Reputation | Calculation of the PageRank for sdafsadf took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.075599670410156e-05s
Believability | Calculation of trust value for sdafsadf took 6.67572021484375e-06s
INFO | --- Analysis for rgsdfg took 3.1409668922424316s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.220008850097656e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0003864765167236328s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2778446674346924s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020827054977416992s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.57763671875e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 8.106231689453125e-06s
INFO | --- Analysis for riese took 2.463491916656494s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 5.173683166503906e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.24698257446289062s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 5.9604644775390625e-06s
INFO | --- Analysis for rijksmuseum took 2.867814540863037s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.9675014019012451s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.24314451217651367s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.57763671875e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 6.4373016357421875e-06s
INFO | --- Analysis for rism took 3.911928653717041s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.17834162712097168s
Availability | VoID file availability check for RISM Authority data took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.24387407302856445s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020854473114013672s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.363059997558594e-05s
Believability | Calculation of trust value for RISM Authority data took 6.67572021484375e-06s
INFO | --- Analysis for rism-authorities took 3.123457670211792s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.23909926414489746s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020785808563232422s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 8.821487426757812e-06s
INFO | --- Analysis for rk took 2.448080539703369s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.06870341300964355s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2744719982147217s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002467632293701172s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.5398643016815186s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.045986175537109375s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004096031188964844s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.27379322052001953s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013875961303710938s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.4350433349609375s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.042586326599121094s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2558157444000244s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0001971721649169922s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.4840457439422607s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.03635859489440918s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2749655246734619s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00015807151794433594s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.527055501937866s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.03624391555786133s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.27288007736206055s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.02018594741821289s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0001513957977294922s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.428764581680298s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.05041360855102539s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2658040523529053s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 4.124641418457031e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.463512420654297s
Availability | SPARQL endpoint availability check for crm took 4.00543212890625e-05s
Availability | VoID file availability check for crm took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for crm took 0.2623414993286133s
Reputation | Calculation of the PageRank for crm took 0.020180940628051758s
Interlinking | Calculation of Degree of Connection for crm took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for crm took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for crm took 3.0517578125e-05s
Believability | Calculation of trust value for crm took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.895857095718384s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.04561042785644531s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2665715217590332s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020087242126464844s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011539459228515625s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.5093939304351807s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04386615753173828s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.2655768394470215s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 4.863739013671875e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.4424142837524414s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04639625549316406s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.2693910598754883s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.000232696533203125s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.465981960296631s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.05088186264038086s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.26181483268737793s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02085590362548828s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.557868957519531e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.486724376678467s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.047063589096069336s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.264894962310791s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.5367431640625e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-deploy took 2.549406051635742s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.04958510398864746s
Availability | VoID file availability check for digitaleconomy took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.28089308738708496s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020743846893310547s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.0517578125e-05s
Believability | Calculation of trust value for digitaleconomy took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.453321695327759s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04075980186462402s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2762906551361084s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014734268188476562s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.4572837352752686s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.040419816970825195s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00036406517028808594s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.25934505462646484s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020445823669433594s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.6253204345703125e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.7987232208251953s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.029273986816406e-05s
Availability | VoID file availability check for enaktingpsi took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.26365208625793457s
Reputation | Calculation of the PageRank for enaktingpsi took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.123283386230469e-05s
Believability | Calculation of trust value for enaktingpsi took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.8750357627868652s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.043951988220214844s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.26288819313049316s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020770549774169922s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00018453598022460938s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.478440999984741s
Availability | SPARQL endpoint availability check for epsrc took 0.04747891426086426s
Availability | VoID file availability check for epsrc took 0.00021600723266601562s
Completeness | Calculation of interlinking completeness for epsrc took 0.2855112552642822s
Reputation | Calculation of the PageRank for epsrc took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for epsrc took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for epsrc took 6.031990051269531e-05s
Believability | Calculation of trust value for epsrc took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.522012233734131s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.04378867149353027s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.2743954658508301s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.106231689453125e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-era took 2.498250722885132s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.05031561851501465s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.2814004421234131s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.0001049041748046875s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.5023274421691895s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.291534423828125e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.27215576171875s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.075599670410156e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-foreign took 3.005704879760742s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.04693126678466797s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2829458713531494s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.226799011230469e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.529292345046997s
Availability | SPARQL endpoint availability check for fun took 0.04306387901306152s
Availability | VoID file availability check for fun took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for fun took 0.2726583480834961s
Reputation | Calculation of the PageRank for fun took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for fun took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for fun took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for fun took 7.605552673339844e-05s
Believability | Calculation of trust value for fun took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.4803097248077393s
Availability | SPARQL endpoint availability check for gdlc took 0.04273247718811035s
Availability | VoID file availability check for gdlc took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for gdlc took 0.2615225315093994s
Reputation | Calculation of the PageRank for gdlc took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.937980651855469e-05s
Believability | Calculation of trust value for gdlc took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.4700162410736084s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.047359466552734375s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2677042484283447s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011563301086425781s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.4598047733306885s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.047103166580200195s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2585744857788086s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00013184547424316406s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.491262674331665s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.04414868354797363s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2766916751861572s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02066946029663086s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001392364501953125s
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.5806803703308105s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.04329037666320801s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.27083373069763184s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02098369598388672s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 8.320808410644531e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.5099093914031982s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.04049944877624512s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2963094711303711s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.021559476852416992s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.002146005630493164s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 0.00017523765563964844s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.514578342437744s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.05240774154663086s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.28800511360168457s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020144939422607422s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007219314575195312s
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 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.5390732288360596s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.04298257827758789s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.281505823135376s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020901918411254883s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016689300537109375s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.5482945442199707s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.052442073822021484s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.27895236015319824s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.0001494884490966797s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.5884552001953125s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04578042030334473s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2681746482849121s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.437301635742188e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.505889892578125s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0492403507232666s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.2838170528411865s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001575946807861328s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.4618520736694336s
Availability | SPARQL endpoint availability check for notube took 0.043062686920166016s
Availability | VoID file availability check for notube took 0.0003414154052734375s
Completeness | Calculation of interlinking completeness for notube took 0.27395129203796387s
Reputation | Calculation of the PageRank for notube took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for notube took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for notube took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for notube took 4.363059997558594e-05s
Believability | Calculation of trust value for notube took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.4206926822662354s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.05813765525817871s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.2825155258178711s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00013446807861328125s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.600165843963623s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.04187202453613281s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2560443878173828s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.021227121353149414s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00017333030700683594s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-oai took 2.5014939308166504s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.029273986816406e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.27864623069763184s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.987732410430908s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.05093193054199219s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.2903306484222412s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.653236389160156e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-os took 2.55971097946167s
Availability | SPARQL endpoint availability check for photos took 0.0455470085144043s
Availability | VoID file availability check for photos took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for photos took 0.2634544372558594s
Reputation | Calculation of the PageRank for photos took 0.027837276458740234s
Interlinking | Calculation of Degree of Connection for photos took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for photos took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for photos took 9.512901306152344e-05s
Believability | Calculation of trust value for photos took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.489440679550171s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.03542757034301758s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.2774198055267334s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011181831359863281s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.4663655757904053s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0392000675201416s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2521536350250244s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019502639770507812s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.4420385360717773s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.06118965148925781s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.2592620849609375s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00013637542724609375s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.523254632949829s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.04263114929199219s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.2816166877746582s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.441375732421875e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.522207260131836s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.05025005340576172s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.26075005531311035s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012755393981933594s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.5562708377838135s
Availability | SPARQL endpoint availability check for roni took 0.045752525329589844s
Availability | VoID file availability check for roni took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for roni took 0.2723522186279297s
Reputation | Calculation of the PageRank for roni took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for roni took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for roni took 2.9325485229492188e-05s
Believability | Calculation of trust value for roni took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.4954452514648438s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.04335141181945801s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.28455543518066406s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.000225067138671875s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.541349172592163s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04287552833557129s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.26725292205810547s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010919570922851562s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.481865167617798s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.04112672805786133s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.26181697845458984s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.679794311523438e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.4944024085998535s
Availability | SPARQL endpoint availability check for webconf took 0.05392313003540039s
Availability | VoID file availability check for webconf took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for webconf took 0.28292059898376465s
Reputation | Calculation of the PageRank for webconf took 0.021204233169555664s
Interlinking | Calculation of Degree of Connection for webconf took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for webconf took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010704994201660156s
Believability | Calculation of trust value for webconf took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-webconf took 12.916180849075317s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.04989504814147949s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.29770851135253906s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020678997039794922s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0009436607360839844s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 9.226799011230469e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.5936388969421387s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.0350804328918457s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.268543004989624s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00020456314086914062s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.4759950637817383s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.053876399993896484s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.2664978504180908s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.0207366943359375s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.202957153320312e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.4699833393096924s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.506111145019531e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.2713000774383545s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.24249267578125e-05s
Believability | Calculation of trust value for RKB Explorer Data took 7.3909759521484375e-06s
INFO | --- Analysis for rkb_explorer_data took 2.949636459350586s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.4838523864746094s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.29158759117126465s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.021251201629638672s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0008912086486816406s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 9.489059448242188e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 8.821487426757812e-06s
INFO | --- Analysis for roceeh-road took 3.8547492027282715s
Availability | SPARQL endpoint availability check for The Rosetta Project took 3.981590270996094e-05s
Availability | VoID file availability check for The Rosetta Project took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.2802004814147949s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.02099609375s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.2901763916015625e-05s
Believability | Calculation of trust value for The Rosetta Project took 8.821487426757812e-06s
INFO | --- Analysis for rosetta-project took 2.9444825649261475s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.1961669921875e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.2734956741333008s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.075599670410156e-05s
Believability | Calculation of trust value for ontology terrorist attack took 8.58306884765625e-06s
INFO | --- Analysis for ROSHANI took 3.566107988357544s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.2438507080078125e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.27112436294555664s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.4809112548828125e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 7.3909759521484375e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.4267449378967285s
Availability | SPARQL endpoint availability check for x took 4.267692565917969e-05s
Availability | VoID file availability check for x took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for x took 0.2568511962890625s
Reputation | Calculation of the PageRank for x took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for x took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for x took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for x took 3.314018249511719e-05s
Believability | Calculation of trust value for x took 8.58306884765625e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.4303300380706787s
Availability | SPARQL endpoint availability check for Rpm Find took 3.933906555175781e-05s
Availability | VoID file availability check for Rpm Find took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.266402006149292s
Reputation | Calculation of the PageRank for Rpm Find took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.0994415283203125e-05s
Believability | Calculation of trust value for Rpm Find took 8.344650268554688e-06s
INFO | --- Analysis for rpm_find took 2.885211706161499s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.2438507080078125e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0009918212890625s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.2512385845184326s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.508827209472656e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 8.106231689453125e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.6057071685791016s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.315376281738281e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2557835578918457s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020727157592773438s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 8.034706115722656e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 8.58306884765625e-06s
INFO | --- Analysis for rubentaelman took 2.8146793842315674s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.363059997558594e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.26502251625061035s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.249282836914062e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 7.867813110351562e-06s
INFO | --- Analysis for rubenverborgh took 3.311619758605957s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.8239805698395s
Availability | VoID file availability check for Russian Universities Specialities took 0.0007574558258056641s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.7109410762786865s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.02103900909423828s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.57763671875e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 8.821487426757812e-06s
INFO | --- Analysis for russian-universities-specialities took 678.0300815105438s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.291534423828125e-05s
Availability | VoID file availability check for RuThes Cloud took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.7006232738494873s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.0279159545898438e-05s
Believability | Calculation of trust value for RuThes Cloud took 7.867813110351562e-06s
INFO | --- Analysis for ruthes took 4.62125039100647s
Availability | SPARQL endpoint availability check for RxNorm took 4.076957702636719e-05s
Availability | VoID file availability check for RxNorm took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2690718173980713s
Reputation | Calculation of the PageRank for RxNorm took 0.020261764526367188s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.2901763916015625e-05s
Believability | Calculation of trust value for RxNorm took 7.62939453125e-06s
INFO | --- Analysis for rxnorm took 3.422654151916504s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.187011003494263s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2450551986694336s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.170967102050781e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 5.9604644775390625e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 11.45323133468628s
Availability | SPARQL endpoint availability check for SALDO took 4.029273986816406e-05s
Availability | VoID file availability check for SALDO took 0.00021076202392578125s
Completeness | Calculation of interlinking completeness for SALDO took 0.2747223377227783s
Reputation | Calculation of the PageRank for SALDO took 0.020866870880126953s
Interlinking | Calculation of Degree of Connection for SALDO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.0279159545898438e-05s
Believability | Calculation of trust value for SALDO took 7.152557373046875e-06s
INFO | --- Analysis for saldo took 2.9030849933624268s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.2124178409576416s
Availability | VoID file availability check for SALDO-RDF took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2813117504119873s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for SALDO-RDF took 6.67572021484375e-06s
INFO | --- Analysis for saldo-rdf took 5.655636787414551s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6088762283325195s
Availability | VoID file availability check for SALDOM-RDF took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.26293182373046875s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.6716461181640625e-05s
Believability | Calculation of trust value for SALDOM-RDF took 6.4373016357421875e-06s
INFO | --- Analysis for saldom-rdf took 5.126909017562866s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.2438507080078125e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2516179084777832s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010395050048828125s
Believability | Calculation of trust value for Salzburgerland DE took 7.152557373046875e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.1950151920318604s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.220008850097656e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.2731444835662842s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010561943054199219s
Believability | Calculation of trust value for Salzburgerland EN took 6.67572021484375e-06s
INFO | --- Analysis for salzburgerland-com-en took 2.945228338241577s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.38690185546875e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.2646512985229492s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010395050048828125s
Believability | Calculation of trust value for Salzburgerland IT took 8.344650268554688e-06s
INFO | --- Analysis for salzburgerland-com-it took 2.908025026321411s
Availability | SPARQL endpoint availability check for sameAs.org took 3.981590270996094e-05s
Availability | VoID file availability check for sameAs.org took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.2911503314971924s
Reputation | Calculation of the PageRank for sameAs.org took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 3.147125244140625e-05s
Believability | Calculation of trust value for sameAs.org took 8.106231689453125e-06s
INFO | --- Analysis for sameas-org took 2.9494247436523438s
Availability | SPARQL endpoint availability check for sandrart.net took 0.0006258487701416016s
Availability | VoID file availability check for sandrart.net took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.27678823471069336s
Reputation | Calculation of the PageRank for sandrart.net took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.723403930664062e-05s
Believability | Calculation of trust value for sandrart.net took 9.059906005859375e-06s
INFO | --- Analysis for sandrart-net took 3.604288101196289s
Availability | SPARQL endpoint availability check for Taxons  took 1.0243024826049805s
Availability | VoID file availability check for Taxons  took 0.00048732757568359375s
Extra | Recovery of all triples for Taxons  took 29.78732705116272s
Performance | Total latancy measurement for Taxons  took 0.4311544895172119s
Amount of data | Number of triples check for Taxons  took 2.5591022968292236s
Interoperability | New terms check for Taxons  took 1.9164891242980957s
Versatility | Languages check for Taxons  took 40.71613955497742s
Interpretability | Number of blank nodes check for Taxons  took 1.2137253284454346s
Security | Check HTTPS for Taxons  took 0.23678898811340332s
Interpretability | RDF structures check for Taxons  took 1.4907052516937256s
Versatility | Serialization formats check for Taxons  took 0.5921878814697266s
Availability | RDF dump link check for Taxons  took 0.29035472869873047s
License | MR license check for Taxons  took 1.9231235980987549s
License | HR license check for Taxons  took 2.233656883239746s
Amount of data | Number of property check for Taxons  took 0.18180632591247559s
Understandability | Number of label check for Taxons  took 4.441084384918213s
Understandability | URI regex check for Taxons  took 0.7928144931793213s
Understandability | Vocabs check for Taxons  took 0.33945298194885254s
Verifiability | Authors check for Taxons  took 0.10916924476623535s
Verifiability | Publishers check for Taxons  took 0.0871281623840332s
Performance | Throughput check for Taxons  took 10.437010049819946s
Amount of data | Check the number of entities for Taxons  took 6.937980651855469e-05s
Verifiability | Contribs. check for Taxons  took 0.0920557975769043s
Interlinking | sameAs chians check for Taxons  took 0.1514585018157959s
Interlinking | skos check for Taxons  took 0.15437936782836914s
Interlinking | skos check for Taxons  took 0.08681511878967285s
Timeliness | dataset update frequency check for Taxons  took 0.49272727966308594s
Currency | Creation date check for Taxons  took 0.20764970779418945s
Currency | Modification date check for Taxons  took 0.22682523727416992s
Rep.Conc. | URIs length for Taxons  took 10.356035709381104s
Interoperability | New vocabularies check for Taxons  took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.11033415794372559s
Accuracy | Check Functional Property for Taxons  took 0.47387170791625977s
Accuracy | Check Inverse Functional Property for Taxons  took 0.3687307834625244s
Accuracy | Check Empty annotation labels for Taxons  took 4.990129470825195s
Accuracy | Check White space in annotation for Taxons  took 0.30557847023010254s
Accuracy | Check Datatype consistency for Taxons  took 0.26778101921081543s
Consistency | Disjoint class check for Taxons  took 0.12466216087341309s
Consistency | Check Misplaced properties for Taxons  took 4.039097547531128s
Consistency | Misplaced classes for Taxons  took 0.9726667404174805s
Consistency | Check Ontology hijacking for Taxons  took 5.333472728729248s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.21268892288208s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.63421368598938s
Conciseness | Check Extensional conciseness for Taxons  took 0.28876304626464844s
Conciseness | Check Intensional conciseness for Taxons  took 0.30365991592407227s
Security | Sign check for Taxons  took 1.9920146465301514s
Availability | Check URIs Dereferenciability for Taxons  took 2454.51748752594s
Completeness | Calculation of interlinking completeness for Taxons  took 1.2180798053741455s
Reputation | Calculation of the PageRank for Taxons  took 0.021783113479614258s
Interlinking | Calculation of Degree of Connection for Taxons  took 6.008148193359375e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Taxons  took 0.0001266002655029297s
Interoperability | Check the re-using of existing vocabs for Taxons  took 2.384185791015625e-06s
Believability | Calculation of trust value for Taxons  took 8.821487426757812e-06s
INFO | --- Analysis for sandre took 2659.781812429428s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.7940270900726318s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0004093647003173828s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.27613115310668945s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.02007436752319336s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 4.76837158203125e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 8.106231689453125e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 7.222460031509399s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 271.024617433548s
Availability | VoID file availability check for Santillana Guide Dataset took 0.001157522201538086s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.7473068237304688s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.02067399024963379s
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 9.5367431640625e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 7.62939453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 718.5699152946472s
Availability | SPARQL endpoint availability check for SATAR test  took 4.57763671875e-05s
Availability | VoID file availability check for SATAR test  took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.7187507152557373s
Reputation | Calculation of the PageRank for SATAR test  took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for SATAR test  took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.8848648071289062e-05s
Believability | Calculation of trust value for SATAR test  took 7.62939453125e-06s
INFO | --- Analysis for SATAR_test took 6.088634252548218s
Availability | SPARQL endpoint availability check for SCBG Data took 22.4696307182312s
Availability | VoID file availability check for SCBG Data took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.26063084602355957s
Reputation | Calculation of the PageRank for SCBG Data took 0.02014303207397461s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 7.557868957519531e-05s
Believability | Calculation of trust value for SCBG Data took 8.58306884765625e-06s
INFO | --- Analysis for SCBG-Data took 55.4313325881958s
Availability | SPARQL endpoint availability check for schema.org took 4.100799560546875e-05s
Availability | VoID file availability check for schema.org took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for schema.org took 0.2683830261230469s
Reputation | Calculation of the PageRank for schema.org took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for schema.org took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.1948089599609375e-05s
Believability | Calculation of trust value for schema.org took 7.62939453125e-06s
INFO | --- Analysis for schema-org took 2.923555374145508s
Availability | SPARQL endpoint availability check for Schemantra took 4.1961669921875e-05s
Availability | VoID file availability check for Schemantra took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Schemantra took 0.2702767848968506s
Reputation | Calculation of the PageRank for Schemantra took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Schemantra took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Schemantra took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.86102294921875e-05s
Believability | Calculation of trust value for Schemantra took 7.152557373046875e-06s
INFO | --- Analysis for Schemantra took 3.255690097808838s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.7515158653259277s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2790958881378174s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.170967102050781e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 8.58306884765625e-06s
INFO | --- Analysis for schemapedia took 5.60589075088501s
Availability | SPARQL endpoint availability check for scholarlydata took 3.8623809814453125e-05s
Availability | VoID file availability check for scholarlydata took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.28484416007995605s
Reputation | Calculation of the PageRank for scholarlydata took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.8371810913085938e-05s
Believability | Calculation of trust value for scholarlydata took 7.62939453125e-06s
INFO | --- Analysis for scholarlydata took 2.945563316345215s
Availability | SPARQL endpoint availability check for Scholarometer took 4.506111145019531e-05s
Availability | VoID file availability check for Scholarometer took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.27872467041015625s
Reputation | Calculation of the PageRank for Scholarometer took 0.019986867904663086s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.678436279296875e-05s
Believability | Calculation of trust value for Scholarometer took 7.3909759521484375e-06s
INFO | --- Analysis for scholarometer took 7.07685399055481s
Availability | SPARQL endpoint availability check for Science Commons took 3.9577484130859375e-05s
Availability | VoID file availability check for Science Commons took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Science Commons took 0.2368919849395752s
Reputation | Calculation of the PageRank for Science Commons took 0.020298242568969727s
Interlinking | Calculation of Degree of Connection for Science Commons took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.8848648071289062e-05s
Believability | Calculation of trust value for Science Commons took 1.1920928955078125e-05s
INFO | --- Analysis for science_commons took 2.803875207901001s
Availability | SPARQL endpoint availability check for ScienceWise took 4.744529724121094e-05s
Availability | VoID file availability check for ScienceWise took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2732548713684082s
Reputation | Calculation of the PageRank for ScienceWise took 0.020819425582885742s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.314018249511719e-05s
Believability | Calculation of trust value for ScienceWise took 7.62939453125e-06s
INFO | --- Analysis for sciencewise took 2.976189613342285s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 5.555152893066406e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.24780750274658203s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020163536071777344s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.86102294921875e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 5.245208740234375e-06s
INFO | --- Analysis for scoreboard took 7.212949991226196s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.482269287109375e-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.0006382465362548828s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.27495527267456055s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020581483840942383s
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.5367431640625e-06s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.0279159545898438e-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 16.12017822265625s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.2438507080078125e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.2954270839691162s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 2.956390380859375e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 7.867813110351562e-06s
INFO | --- Analysis for SDG took 3.217921495437622s
Availability | SPARQL endpoint availability check for sears.com took 5.8650970458984375e-05s
Availability | VoID file availability check for sears.com took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for sears.com took 0.27016377449035645s
Reputation | Calculation of the PageRank for sears.com took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for sears.com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for sears.com took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.437301635742188e-05s
Believability | Calculation of trust value for sears.com took 7.3909759521484375e-06s
INFO | --- Analysis for sears took 4.484764575958252s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 4.6276092529296875s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.28842830657958984s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 7.915496826171875e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.4836273193359375e-06s
INFO | --- Analysis for sec-rdfabout took 14.627912282943726s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.70924711227417s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.26328277587890625s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.368492126464844e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for secold took 168.90271615982056s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 3.981590270996094e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.00021338462829589844s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.32033395767211914s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.02010202407836914s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.8133392333984375e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 7.152557373046875e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.546200752258301s
Availability | SPARQL endpoint availability check for semanlink took 8.630752563476562e-05s
Availability | VoID file availability check for semanlink took 0.0015187263488769531s
Completeness | Calculation of interlinking completeness for semanlink took 0.26984238624572754s
Reputation | Calculation of the PageRank for semanlink took 0.021312236785888672s
Interlinking | Calculation of Degree of Connection for semanlink took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0009031295776367188s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001666545867919922s
Believability | Calculation of trust value for semanlink took 8.106231689453125e-06s
INFO | --- Analysis for semanlink took 183.4467806816101s
Availability | SPARQL endpoint availability check for Semantic Library took 3.910064697265625e-05s
Availability | VoID file availability check for Semantic Library took 0.00032973289489746094s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.2668905258178711s
Reputation | Calculation of the PageRank for Semantic Library took 0.02045297622680664s
Interlinking | Calculation of Degree of Connection for Semantic Library took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic Library took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.7418136596679688e-05s
Believability | Calculation of trust value for Semantic Library took 1.4543533325195312e-05s
INFO | --- Analysis for semantic-library took 3.833495855331421s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.076957702636719e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.27773070335388184s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 2.9087066650390625e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 7.62939453125e-06s
INFO | --- Analysis for semantic-profiling-network took 2.918016195297241s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.07012391090393066s
Availability | VoID file availability check for Semantic Universe Data took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.265073299407959s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.0517578125e-05s
Believability | Calculation of trust value for Semantic Universe Data took 7.867813110351562e-06s
INFO | --- Analysis for semantic-universe took 2.5318963527679443s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 31.668351888656616s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2846198081970215s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.02077627182006836s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011324882507324219s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 8.821487426757812e-06s
INFO | --- Analysis for semantic-web-dog-food took 85.10629105567932s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 5.888938903808594e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0004124641418457031s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2620878219604492s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.026027202606201172s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.696846008300781e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 8.106231689453125e-06s
INFO | --- Analysis for semantic-web-grundlagen took 12.94682240486145s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.220008850097656e-05s
Availability | VoID file availability check for semantic-web-journal took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.265841007232666s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.314018249511719e-05s
Believability | Calculation of trust value for semantic-web-journal took 8.58306884765625e-06s
INFO | --- Analysis for semantic-web-journal took 3.3849856853485107s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.3085923194885254s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020705461502075195s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.463859558105469e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 4.76837158203125e-06s
INFO | --- Analysis for semantic-xbrl took 3.4887077808380127s
Availability | SPARQL endpoint availability check for Semantic Bible took 4.124641418457031e-05s
Availability | VoID file availability check for Semantic Bible took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2765364646911621s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.24249267578125e-05s
Believability | Calculation of trust value for Semantic Bible took 8.821487426757812e-06s
INFO | --- Analysis for semantic_bible took 2.9420065879821777s
Availability | SPARQL endpoint availability check for SemanticQuran took 4.027684926986694s
Availability | VoID file availability check for SemanticQuran took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.24499082565307617s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.05718994140625e-05s
Believability | Calculation of trust value for SemanticQuran took 6.198883056640625e-06s
INFO | --- Analysis for semanticquran took 13.043758153915405s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.4345855712890625e-05s
Availability | VoID file availability check for SemanticTweet took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.25633788108825684s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02082538604736328s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.8650970458984375e-05s
Believability | Calculation of trust value for SemanticTweet took 7.152557373046875e-06s
INFO | --- Analysis for semantictweet took 3.7398452758789062s
Availability | SPARQL endpoint availability check for semanticweb.org took 5.602836608886719e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.28735971450805664s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.843971252441406e-05s
Believability | Calculation of trust value for semanticweb.org took 7.62939453125e-06s
INFO | --- Analysis for semanticweb-org took 27.614346265792847s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.09923553466796875s
Availability | VoID file availability check for Semantic CrunchBase took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.25104427337646484s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.02149820327758789s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 7.152557373046875e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 8.344650268554688e-06s
INFO | --- Analysis for semsol-crunchbase took 2.4920730590820312s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.0531158447265625e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.26679372787475586s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 2.86102294921875e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 8.58306884765625e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.971580982208252s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.26024818420410156s
Availability | VoID file availability check for SentimentWortschatz took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2513883113861084s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.100799560546875e-05s
Believability | Calculation of trust value for SentimentWortschatz took 7.3909759521484375e-06s
INFO | --- Analysis for sentiws took 3.5120692253112793s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.133352518081665s
Availability | VoID file availability check for seoul-bike-data took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.2621273994445801s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.409385681152344e-05s
Believability | Calculation of trust value for seoul-bike-data took 6.9141387939453125e-06s
INFO | --- Analysis for seoul-bike-data took 72.76761984825134s
Availability | SPARQL endpoint availability check for Serendipity took 8.20213794708252s
Availability | VoID file availability check for Serendipity took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2600870132446289s
Reputation | Calculation of the PageRank for Serendipity took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Serendipity took 8.344650268554688e-05s
Believability | Calculation of trust value for Serendipity took 7.152557373046875e-06s
INFO | --- Analysis for serendipity took 15.88423490524292s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 5.364418029785156e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.27133750915527344s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 2.8848648071289062e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 7.152557373046875e-06s
INFO | --- Analysis for Sherry_Wine took 2.593984365463257s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.2438507080078125e-05s
Availability | VoID file availability check for Sherry Wine took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2694098949432373s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.8371810913085938e-05s
Believability | Calculation of trust value for Sherry Wine took 1.0013580322265625e-05s
INFO | --- Analysis for Sherry_Wine_ took 2.825015068054199s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.22939801216125488s
Availability | VoID file availability check for Shoah victims? names took 0.0005598068237304688s
Extra | Recovery of all triples for Shoah victims? names took 1.886460542678833s
Performance | Total latancy measurement for Shoah victims? names took 0.43480420112609863s
Amount of data | Number of triples check for Shoah victims? names took 1.527827262878418s
Interoperability | New terms check for Shoah victims? names took 1.6442880630493164s
Versatility | Languages check for Shoah victims? names took 8.56688666343689s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.0550718307495117s
Security | Check HTTPS for Shoah victims? names took 0.22960162162780762s
Interpretability | RDF structures check for Shoah victims? names took 0.13868379592895508s
Versatility | Serialization formats check for Shoah victims? names took 0.351839542388916s
Availability | RDF dump link check for Shoah victims? names took 0.2137758731842041s
License | MR license check for Shoah victims? names took 0.4864466190338135s
License | HR license check for Shoah victims? names took 10.85025668144226s
Amount of data | Number of property check for Shoah victims? names took 0.13558483123779297s
Understandability | Number of label check for Shoah victims? names took 1.3751654624938965s
Understandability | URI regex check for Shoah victims? names took 0.5468807220458984s
Understandability | Vocabs check for Shoah victims? names took 0.13453388214111328s
Verifiability | Authors check for Shoah victims? names took 0.22356939315795898s
Verifiability | Publishers check for Shoah victims? names took 0.28551363945007324s
Performance | Throughput check for Shoah victims? names took 10.377633571624756s
Amount of data | Check the number of entities for Shoah victims? names took 0.00010752677917480469s
Verifiability | Contribs. check for Shoah victims? names took 0.0696096420288086s
Interlinking | sameAs chians check for Shoah victims? names took 0.19115471839904785s
Interlinking | skos check for Shoah victims? names took 0.3512406349182129s
Interlinking | skos check for Shoah victims? names took 0.05809974670410156s
Timeliness | dataset update frequency check for Shoah victims? names took 0.3833189010620117s
Currency | Creation date check for Shoah victims? names took 0.1583118438720703s
Currency | Modification date check for Shoah victims? names took 0.17473435401916504s
Rep.Conc. | URIs length for Shoah victims? names took 3.266317844390869s
Interoperability | New vocabularies check for Shoah victims? names took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.08526420593261719s
Accuracy | Check Functional Property for Shoah victims? names took 0.12057638168334961s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.0949559211730957s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.6053647994995117s
Accuracy | Check White space in annotation for Shoah victims? names took 0.028216838836669922s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.02817535400390625s
Consistency | Disjoint class check for Shoah victims? names took 0.21829462051391602s
Consistency | Check Misplaced properties for Shoah victims? names took 2.362325668334961s
Consistency | Misplaced classes for Shoah victims? names took 0.19835233688354492s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.584855318069458s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.1741087436676025s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.261225700378418s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.03023076057434082s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.11708188056945801s
Security | Sign check for Shoah victims? names took 0.6278040409088135s
Availability | Check URIs Dereferenciability for Shoah victims? names took 2394.0427873134613s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 1.2184927463531494s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.023723125457763672s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.430511474609375e-06s
Believability | Calculation of trust value for Shoah victims? names took 7.62939453125e-06s
INFO | --- Analysis for shoah-victims-names took 2506.680393218994s
Availability | SPARQL endpoint availability check for Person took 7.152557373046875e-05s
Availability | VoID file availability check for Person took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Person took 0.2706308364868164s
Reputation | Calculation of the PageRank for Person took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for Person took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Person took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Person took 3.0994415283203125e-05s
Believability | Calculation of trust value for Person took 8.58306884765625e-06s
INFO | --- Analysis for Shripriya_Dubey took 3.815401077270508s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.3392181396484375e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.7200407981872559s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.956390380859375e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 6.9141387939453125e-06s
INFO | --- Analysis for Shutterstock took 2.886011838912964s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.124641418457031e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.26444578170776367s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 2.9802322387695312e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 6.9141387939453125e-06s
INFO | --- Analysis for simile_data_collection took 3.389293670654297s
Availability | SPARQL endpoint availability check for SIMPLE took 4.410743713378906e-05s
Availability | VoID file availability check for SIMPLE took 0.0011553764343261719s
Completeness | Calculation of interlinking completeness for SIMPLE took 1.4873933792114258s
Reputation | Calculation of the PageRank for SIMPLE took 0.02172064781188965s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 5.3882598876953125e-05s
Believability | Calculation of trust value for SIMPLE took 9.059906005859375e-06s
INFO | --- Analysis for simple took 1809.6978092193604s
Availability | SPARQL endpoint availability check for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 4.5299530029296875e-05s
Availability | VoID file availability check for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.2752368450164795s
Reputation | Calculation of the PageRank for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 1.33514404296875e-05s
Believability | Calculation of trust value for 2019-2022 Analysis of the π Index in China's Life Sciences and Basic Medicine took 7.867813110351562e-06s
INFO | --- Analysis for sinh-CLSPIRData took 4.159555196762085s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.73416233062744s
Availability | VoID file availability check for SITC-V4 took 0.000827789306640625s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.713994026184082s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020203590393066406s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.100799560546875e-05s
Believability | Calculation of trust value for SITC-V4 took 5.4836273193359375e-06s
INFO | --- Analysis for sitc-v4 took 126.47019696235657s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.2438507080078125e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.26737046241760254s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.172325134277344e-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 14.336963176727295s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.220008850097656e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.2780764102935791s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 2.8371810913085938e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 7.62939453125e-06s
INFO | --- Analysis for slideshare2rdf took 2.9361207485198975s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 6.413459777832031e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.27345705032348633s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020296812057495117s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.075599670410156e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 9.059906005859375e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 3.4472222328186035s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.7802605628967285s
Availability | VoID file availability check for Linked Stage Graph took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.27963900566101074s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 4.8160552978515625e-05s
Believability | Calculation of trust value for Linked Stage Graph took 7.867813110351562e-06s
INFO | --- Analysis for slod took 3.822094202041626s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.124641418457031e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.2772212028503418s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.02032780647277832s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.0040740966796875e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 7.152557373046875e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.9548392295837402s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.6302914619445801s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0002846717834472656s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 126.89042282104492s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9315626621246338s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.478548765182495s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.906170129776001s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.2230567932129s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 3.1586930751800537s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.2615649700164795s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 11.230649709701538s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.2316441535949707s
License | MR license check for Smart Points Of Interest @PSNC took 0.36716580390930176s
License | HR license check for Smart Points Of Interest @PSNC took 300.195205450058s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.397022008895874s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.6231963634490967s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.7300584316253662s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.3753542900085449s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.21242570877075195s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.26035451889038086s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.004873037338257s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 0.0001823902130126953s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.1970987319946289s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.17705368995666504s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4683680534362793s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.469738245010376s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 5.543848037719727s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.4730715751647949s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.21291327476501465s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 174.30767488479614s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.18198561668395996s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.3466470241546631s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.2789912223815918s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 44.88309025764465s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.6682252883911133s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.5668513774871826s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.18105292320251465s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 93.93678545951843s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.37092661857605s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 40.89745330810547s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.1980929374694824s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 91.23727560043335s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.762028217315674s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5639197826385498s
Security | Sign check for Smart Points Of Interest @PSNC took 0.9203412532806396s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 5.80870246887207s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 1.5283634662628174s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00011491775512695312s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 5.245208740234375e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Smart_POI_dataset took 2336.4269740581512s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 6.214597940444946s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0008208751678466797s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.26063108444213867s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.886222839355469e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 7.867813110351562e-06s
INFO | --- Analysis for smartlink took 16.398253679275513s
Availability | SPARQL endpoint availability check for SNIK took 0.4695720672607422s
Availability | VoID file availability check for SNIK took 0.0006973743438720703s
Extra | Recovery of all triples for SNIK took 7.574014902114868s
Performance | Total latancy measurement for SNIK took 0.9909043312072754s
Amount of data | Number of triples check for SNIK took 0.2082967758178711s
Interoperability | New terms check for SNIK took 1.377357006072998s
Versatility | Languages check for SNIK took 0.22118663787841797s
Interpretability | Number of blank nodes check for SNIK took 0.20810651779174805s
Interpretability | RDF structures check for SNIK took 0.18539118766784668s
Versatility | Serialization formats check for SNIK took 0.19729304313659668s
Availability | RDF dump link check for SNIK took 0.1947484016418457s
License | MR license check for SNIK took 0.19819402694702148s
License | HR license check for SNIK took 0.2222743034362793s
Amount of data | Number of property check for SNIK took 0.19716620445251465s
Understandability | Number of label check for SNIK took 0.18892359733581543s
Understandability | URI regex check for SNIK took 0.38912081718444824s
Understandability | Vocabs check for SNIK took 0.20829153060913086s
Verifiability | Authors check for SNIK took 0.1971876621246338s
Verifiability | Publishers check for SNIK took 0.19468069076538086s
Performance | Throughput check for SNIK took 11.009682178497314s
Amount of data | Check the number of entities for SNIK took 7.653236389160156e-05s
Verifiability | Contribs. check for SNIK took 0.18662095069885254s
Interlinking | sameAs chians check for SNIK took 0.1976299285888672s
Interlinking | skos check for SNIK took 0.19504666328430176s
Interlinking | skos check for SNIK took 0.18512630462646484s
Timeliness | dataset update frequency check for SNIK took 0.19867706298828125s
Currency | Creation date check for SNIK took 0.39611148834228516s
Currency | Modification date check for SNIK took 0.3950932025909424s
Rep.Conc. | URIs length for SNIK took 1.9692182540893555s
Interoperability | New vocabularies check for SNIK took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.19461894035339355s
Accuracy | Check Functional Property for SNIK took 0.19379925727844238s
Accuracy | Check Inverse Functional Property for SNIK took 0.18802928924560547s
Accuracy | Check Empty annotation labels for SNIK took 0.7706208229064941s
Accuracy | Check White space in annotation for SNIK took 0.02766132354736328s
Accuracy | Check Datatype consistency for SNIK took 0.2146914005279541s
Consistency | Disjoint class check for SNIK took 0.20771527290344238s
Consistency | Check Misplaced properties for SNIK took 0.6892445087432861s
Consistency | Misplaced classes for SNIK took 0.6942455768585205s
Consistency | Check Ontology hijacking for SNIK took 1.712498664855957s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.1481256484985352s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.4494309425354004s
Conciseness | Check Extensional conciseness for SNIK took 0.15777325630187988s
Conciseness | Check Intensional conciseness for SNIK took 0.32549047470092773s
Security | Sign check for SNIK took 0.18451237678527832s
Availability | Check URIs Dereferenciability for SNIK took 663.2205438613892s
Completeness | Calculation of interlinking completeness for SNIK took 0.9439337253570557s
Reputation | Calculation of the PageRank for SNIK took 0.0210573673248291s
Interlinking | Calculation of Degree of Connection for SNIK took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for SNIK took 0.00013709068298339844s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.430511474609375e-06s
Believability | Calculation of trust value for SNIK took 8.58306884765625e-06s
INFO | --- Analysis for snik took 722.8058753013611s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 5.125999450683594e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.7309973239898682s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.218650817871094e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 8.106231689453125e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 4.262155532836914s
Availability | SPARQL endpoint availability check for SocialLink took 2.8607258796691895s
Availability | VoID file availability check for SocialLink took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for SocialLink took 0.26969289779663086s
Reputation | Calculation of the PageRank for SocialLink took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.224082946777344e-05s
Believability | Calculation of trust value for SocialLink took 8.344650268554688e-06s
INFO | --- Analysis for SocialLink took 11.93204402923584s
Availability | SPARQL endpoint availability check for SocialLink took 4.00543212890625e-05s
Availability | VoID file availability check for SocialLink took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2798037528991699s
Reputation | Calculation of the PageRank for SocialLink took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for SocialLink took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for SocialLink took 2.8848648071289062e-05s
Believability | Calculation of trust value for SocialLink took 7.62939453125e-06s
INFO | --- Analysis for sociallink took 3.366194725036621s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.3392181396484375e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.26830148696899414s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.075599670410156e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 7.3909759521484375e-06s
INFO | --- Analysis for SocialRoles took 12.776716470718384s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.30085206031799316s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007274150848388672s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 23.91518545150757s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.5133252143859863s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.22997140884399414s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.465075969696045s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.4490683078765869s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.22555303573608398s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.34240150451660156s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.11403298377990723s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.10542821884155273s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7980034351348877s
License | MR license check for Social Semantic Web Thesaurus took 0.13099455833435059s
License | HR license check for Social Semantic Web Thesaurus took 0.10436511039733887s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.11279296875s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.14186334609985352s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.18759632110595703s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.1122121810913086s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.1304318904876709s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.14132905006408691s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.517302513122559s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 6.890296936035156e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12938857078552246s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.11908292770385742s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11908245086669922s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.10815215110778809s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.09423637390136719s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.21165060997009277s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.19199061393737793s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 2.3516671657562256s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.11713671684265137s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.07874870300292969s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.11316227912902832s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4472470283508301s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012219905853271484s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.10131216049194336s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.35916590690612793s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.09268808364868164s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.1657474040985107s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.4070258140563965s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0001404285430908203s
Security | Sign check for Social Semantic Web Thesaurus took 0.08002829551696777s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 118.28407073020935s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.7092247009277344s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.036064147949219e-05s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.4066696166992188e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 242.92079329490662s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.27441954612731934s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.00023651123046875s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 122.54284739494324s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.003312110900879s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.729557514190674s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.311952114105225s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.20455169677734s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.830355644226074s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2678689956665039s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 12.075876474380493s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.290940523147583s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5005743503570557s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.18477988243103s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.41980671882629395s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.9275729656219482s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.7809367179870605s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4304943084716797s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1822512149810791s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2646822929382324s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.567254543304443s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 5.3882598876953125e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1829979419708252s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1974775791168213s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4883098602294922s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4723026752471924s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.393131494522095s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4965176582336426s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2190847396850586s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 174.07220339775085s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1819779872894287s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.36441898345947266s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3687937259674072s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 44.48849129676819s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.666914224624634s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.575042486190796s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20924615859985352s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 92.60485625267029s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.275124788284302s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 37.15185046195984s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2321045398712158s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 92.02233386039734s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.719470500946045s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5892717838287354s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.8067927360534668s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 5.039029359817505s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9999699592590332s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for Soil_maps took 2306.099627494812s
Availability | SPARQL endpoint availability check for terrorrist ontology took 4.744529724121094e-05s
Availability | VoID file availability check for terrorrist ontology took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.6879756450653076s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.695487976074219e-05s
Believability | Calculation of trust value for terrorrist ontology took 7.62939453125e-06s
INFO | --- Analysis for somya_omer took 4.110809564590454s
Availability | SPARQL endpoint availability check for Sonclubcx took 0.00014591217041015625s
Availability | VoID file availability check for Sonclubcx took 0.0004038810729980469s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.715226411819458s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020191192626953125s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 0.0001380443572998047s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.2159347534179688e-05s
Believability | Calculation of trust value for Sonclubcx took 8.821487426757812e-06s
INFO | --- Analysis for sonclubcx took 5.521060943603516s
Availability | SPARQL endpoint availability check for SORS took 4.38690185546875e-05s
Availability | VoID file availability check for SORS took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for SORS took 0.2703590393066406s
Reputation | Calculation of the PageRank for SORS took 0.02007889747619629s
Interlinking | Calculation of Degree of Connection for SORS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SORS took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for SORS took 5.030632019042969e-05s
Believability | Calculation of trust value for SORS took 5.4836273193359375e-06s
INFO | --- Analysis for sors took 3.9905037879943848s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.315376281738281e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0003199577331542969s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.2800590991973877s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 3.218650817871094e-05s
Believability | Calculation of trust value for Soudy České republiky took 8.344650268554688e-06s
INFO | --- Analysis for soudy--esk--republiky took 3.400611400604248s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.291534423828125e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.701514720916748s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020229101181030273s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.1552734375e-05s
Believability | Calculation of trust value for southampton-ac-uk took 9.059906005859375e-06s
INFO | --- Analysis for southampton-ac-uk took 4.673582553863525s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.2765560150146484s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.26593637466430664s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 8.344650268554688e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.593722581863403s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.291534423828125e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.28206539154052734s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020900249481201172s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 0.00010919570922851562s
Believability | Calculation of trust value for ECS Southampton EPrints took 8.344650268554688e-06s
INFO | --- Analysis for southampton-ecs-eprints took 25.475905418395996s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5821044445037842s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0002837181091308594s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 217.19251680374146s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.2059822082519531s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 9.36480712890625s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.398729085922241s
Versatility | Languages check for Spanish Linguistic Datasets took 48.2578227519989s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 2.139026641845703s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.1254265308380127s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.4246225357055664s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.3665783405303955s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.2943551540374756s
License | MR license check for Spanish Linguistic Datasets took 0.3171989917755127s
License | HR license check for Spanish Linguistic Datasets took 0.5313582420349121s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.34687042236328125s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3425428867340088s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5672316551208496s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.27273106575012207s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.3259882926940918s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2967805862426758s
Performance | Throughput check for Spanish Linguistic Datasets took 11.291131258010864s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.414817810058594e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.2880985736846924s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.29194140434265137s
Interlinking | skos check for Spanish Linguistic Datasets took 0.28575921058654785s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2073962688446045s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.29712414741516113s
Currency | Creation date check for Spanish Linguistic Datasets took 0.6175036430358887s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5896439552307129s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 75.78747320175171s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2849085330963135s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.26823902130126953s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.296511173248291s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9169068336486816s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010248899459838867s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.712589979171753s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.28019070625305176s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 5.169748306274414s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.561064720153809s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 70.62935161590576s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.3558173179626465s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.7480034828186035s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.8992972373962402s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.38731956481933594s
Security | Sign check for Spanish Linguistic Datasets took 0.29193925857543945s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 5.9302449226379395s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.3942453861236572s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.1948089599609375e-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 7.867813110351562e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 541.9452846050262s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.08210039138793945s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2646656036376953s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020818471908569336s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.76837158203125e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 7.152557373046875e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.961038589477539s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.220008850097656e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.25348496437072754s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.02143073081970215s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 3.1948089599609375e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 8.58306884765625e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 3.4108405113220215s
Availability | SPARQL endpoint availability check for SPQR took 3.981590270996094e-05s
Availability | VoID file availability check for SPQR took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for SPQR took 0.25681161880493164s
Reputation | Calculation of the PageRank for SPQR took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for SPQR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for SPQR took 3.0994415283203125e-05s
Believability | Calculation of trust value for SPQR took 6.198883056640625e-06s
INFO | --- Analysis for spqr took 2.895207166671753s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.1484832763671875e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.251039981842041s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.654594421386719e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 7.3909759521484375e-06s
INFO | --- Analysis for springernaturescigraph took 3.791088104248047s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 5.340576171875e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.26732659339904785s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 8.344650268554688e-06s
INFO | --- Analysis for srcmf took 7.772759437561035s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 30.176275491714478s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.264312744140625s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.023215770721435547s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0011873245239257812s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 6.461143493652344e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.049041748046875e-05s
INFO | --- Analysis for ssf took 83.93096280097961s
Availability | SPARQL endpoint availability check for SSF took 4.100799560546875e-05s
Availability | VoID file availability check for SSF took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for SSF took 0.3064253330230713s
Reputation | Calculation of the PageRank for SSF took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for SSF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SSF took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for SSF took 2.956390380859375e-05s
Believability | Calculation of trust value for SSF took 6.4373016357421875e-06s
INFO | --- Analysis for ssf-lexicon took 3.4894797801971436s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.1484832763671875e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.29978275299072266s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020762920379638672s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.600120544433594e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 8.58306884765625e-06s
INFO | --- Analysis for st-andrews-resource-lists took 3.6504414081573486s
Availability | SPARQL endpoint availability check for STAC took 4.172325134277344e-05s
Availability | VoID file availability check for STAC took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for STAC took 0.2882676124572754s
Reputation | Calculation of the PageRank for STAC took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for STAC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for STAC took 3.075599670410156e-05s
Believability | Calculation of trust value for STAC took 8.344650268554688e-06s
INFO | --- Analysis for stac took 3.422149181365967s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.172325134277344e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.2485191822052002s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.147125244140625e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 8.58306884765625e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 3.7898056507110596s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.2438507080078125e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.29619741439819336s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020459413528442383s
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.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.600120544433594e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 6.9141387939453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.341367721557617s
Availability | SPARQL endpoint availability check for Stammbuch took 4.267692565917969e-05s
Availability | VoID file availability check for Stammbuch took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2762422561645508s
Reputation | Calculation of the PageRank for Stammbuch took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.147125244140625e-05s
Believability | Calculation of trust value for Stammbuch took 1.3589859008789062e-05s
INFO | --- Analysis for Stammbuch took 2.36626935005188s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.9012742042541504s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.26325201988220215s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010204315185546875s
Believability | Calculation of trust value for statistics.data.gov.uk took 6.198883056640625e-06s
INFO | --- Analysis for statistics-data-gov-uk took 5.568711519241333s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 5.340576171875e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.2661764621734619s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 3.075599670410156e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 6.9141387939453125e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.886826753616333s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2798023223876953s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.02102494239807129s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.0001087188720703125s
Believability | Calculation of trust value for statusnet-1w6-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-1w6-org took 3.055704355239868s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.27170372009277344s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.02145838737487793s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0009870529174804688s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 7.534027099609375e-05s
Believability | Calculation of trust value for statusnet-20100-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-20100-org took 2.479642391204834s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.26550912857055664s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.414817810058594e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.788058042526245s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2628910541534424s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0009219646453857422s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 9.107589721679688e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.503150701522827s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2558279037475586s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.870529174804688e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.580519199371338s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0011751651763916016s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2489466667175293s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00010800361633300781s
Believability | Calculation of trust value for statusnet-bka-li took 7.62939453125e-06s
INFO | --- Analysis for statusnet-bka-li took 2.574331760406494s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.28174638748168945s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.076957702636719e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.2221999168395996s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.260265588760376s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0009920597076416016s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-ced117-net took 4.2509377002716064s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.2741553783416748s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 4.9591064453125e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.660855770111084s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.26795148849487305s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011229515075683594s
Believability | Calculation of trust value for statusnet-chromic-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.7208235263824463s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.271848201751709s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020175457000732422s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.82012939453125e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.296390056610107s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.257004976272583s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.4419105052948s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.25241899490356445s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.605552673339844e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.3338050842285156s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2656404972076416s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010657310485839844s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.5905821323394775s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.24980974197387695s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.43802809715271s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2733755111694336s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.221366882324219e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.376565933227539s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2630040645599365s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.02171039581298828s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-dtdns-net took 22.395772218704224s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.267012357711792s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.504753112792969e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.4474868774414062s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.25811266899108887s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.224082946777344e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.546313762664795s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.27912378311157227s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02084040641784668s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.608268737792969e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.433895587921143s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.25910449028015137s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.021092891693115234s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 2.5662293434143066s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 5.555152893066406e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.2654707431793213s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.0001823902130126953s
Believability | Calculation of trust value for statusnet-fragdev-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.270399332046509s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2649877071380615s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02015376091003418s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.319450378417969e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.419048309326172s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.27865004539489746s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010800361633300781s
Believability | Calculation of trust value for statusnet-gegeweb-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.6328516006469727s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.26201343536376953s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-glou-org took 2.5457446575164795s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2636387348175049s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020639657974243164s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.0001361370086669922s
Believability | Calculation of trust value for statusnet-gomertronic-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.4068403244018555s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.28233909606933594s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020268917083740234s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-hackerposse-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.958658218383789s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.27591466903686523s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.5299530029296875e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.1823537349700928s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0012547969818115234s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2742156982421875s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020061016082763672s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.274482727050781e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.507017135620117s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2541522979736328s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 5.8650970458984375e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.62939453125e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.503865957260132s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0011925697326660156s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.26679277420043945s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.7670135498046875e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.603288412094116s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.25966644287109375s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.437018156051636s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2521851062774658s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011420249938964844s
Believability | Calculation of trust value for statusnet-jonkman-ca took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.3216049671173096s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 7.128715515136719e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2540140151977539s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.021421432495117188s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 0.00010275840759277344s
Believability | Calculation of trust value for statusnet-kaimi-cc took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4379384517669678s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2596018314361572s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.792213439941406e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.4368433952331543s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2724168300628662s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020595550537109375s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.076957702636719e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.7253482341766357s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.26041078567504883s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.843971252441406e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.3808584213256836s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.001260995864868164s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2600128650665283s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020838260650634766s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.0067901611328125e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.4987473487854004s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2686333656311035s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.021218061447143555s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0009236335754394531s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 7.05718994140625e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.589996814727783s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 7.152557373046875e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.29004406929016113s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.441375732421875e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.6817445755004883s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2673153877258301s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.0001361370086669922s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.4174442291259766s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 8.058547973632812e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2610280513763428s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0010199546813964844s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 6.842613220214844e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.830782413482666s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 5.602836608886719e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.27550554275512695s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00010156631469726562s
Believability | Calculation of trust value for statusnet-lydiastench-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.3843767642974854s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.26358747482299805s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.340576171875e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.4394280910491943s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.30533480644226074s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020522594451904297s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00015282630920410156s
Believability | Calculation of trust value for statusnet-macno-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-macno-org took 2.4957470893859863s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.290477991104126s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007100105285644531s
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 6.67572021484375e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.5332186222076416s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 5.435943603515625e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.00038313865661621094s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2496480941772461s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.58306884765625e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.197402477264404s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.25870704650878906s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00017118453979492188s
Believability | Calculation of trust value for statusnet-morphtown-de took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.4903335571289062s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0008590221405029297s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.26631832122802734s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020560741424560547s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 6.0558319091796875e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00010156631469726562s
Believability | Calculation of trust value for statusnet-mrblog-nl took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.3872416019439697s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.25901031494140625s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.385725498199463s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.001234292984008789s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.2685990333557129s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 7.62939453125e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.539238214492798s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.25000596046447754s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010943412780761719s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.385979175567627s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.000782012939453125s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2540254592895508s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.9604644775390625e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.4856765270233154s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.25023555755615234s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.389617919921875e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.4279773235321045s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0013644695281982422s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.2606642246246338s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020999431610107422s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 9.441375732421875e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.3145933151245117s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.24759554862976074s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.9114227294921875e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.62939453125e-06s
INFO | --- Analysis for statusnet-panda-id-au took 2.9099905490875244s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2746431827545166s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020329952239990234s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.608268737792969e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.543743371963501s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.2738068103790283s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.915496826171875e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.8025646209716797s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2687849998474121s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002524852752685547s
Believability | Calculation of trust value for statusnet-postblue-info took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.869169235229492s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.26100659370422363s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.866455078125e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-progval-net took 2.5168254375457764s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 5.435943603515625e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.27286267280578613s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011491775512695312s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.9547109603881836s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2728159427642822s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020879745483398438s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.255114793777466s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.25174403190612793s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021648406982421875s
Believability | Calculation of trust value for statusnet-quitter-se took 7.62939453125e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.6021249294281006s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.3012838363647461s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010228157043457031s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 3.022416830062866s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.2591266632080078s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-recit-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-recit-org took 4.689547538757324s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.27759623527526855s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001480579376220703s
Believability | Calculation of trust value for statusnet-russwurm-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.6802101135253906s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 5.435943603515625e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2790970802307129s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.106231689453125e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.754595756530762s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2862365245819092s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 9.322166442871094e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.554216146469116s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2705094814300537s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.00010061264038085938s
Believability | Calculation of trust value for statusnet-scoffoni-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.4684946537017822s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 5.125999450683594e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.2845323085784912s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-sebseb01-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.5105910301208496s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.28520727157592773s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.284924030303955s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.26347923278808594s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020108699798583984s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021123886108398438s
Believability | Calculation of trust value for statusnet-skilledtests-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 2.942627191543579s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2598412036895752s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00011038780212402344s
Believability | Calculation of trust value for statusnet-somsants-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.547125816345215s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2678818702697754s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00013399124145507812s
Believability | Calculation of trust value for statusnet-soucy-cc took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.490530490875244s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 5.2928924560546875e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2697746753692627s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02119898796081543s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 5.8650970458984375e-05s
Believability | Calculation of trust value for statusnet-spip-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-spip-org took 3.4799137115478516s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.253711462020874s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.45525860786438s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.28484225273132324s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00012445449829101562s
Believability | Calculation of trust value for statusnet-ssweeny-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.542165994644165s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.25423336029052734s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020117759704589844s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022268295288085938s
Believability | Calculation of trust value for statusnet-status-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-status-net took 3.662123441696167s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2884054183959961s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.3655238151550293s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.26934337615966797s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020315170288085938s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.298324584960938e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.435098648071289s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.28494811058044434s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012373924255371094s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.8486475944519043s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2714114189147949s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020241975784301758s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.102524757385254s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.26137852668762207s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010395050048828125s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.8117141723632812s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2560861110687256s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.02014780044555664s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.00543212890625e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.5135483741760254s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2602229118347168s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.985664367675781e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.603586435317993s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.26714062690734863s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.790855407714844e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.3094942569732666s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 7.43865966796875e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.26673007011413574s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for steak took 2.9803130626678467s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.1961669921875e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.29151058197021484s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020207881927490234s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.316734313964844e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 5.9604644775390625e-06s
INFO | --- Analysis for stitch-rameau took 4.023588180541992s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.6312017440795898s
Availability | VoID file availability check for Stone Tech Square took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.26416850090026855s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020346641540527344s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.1920928955078125e-05s
Believability | Calculation of trust value for Stone Tech Square took 7.152557373046875e-06s
INFO | --- Analysis for stone-tech-square-data took 4.600867986679077s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.982948303222656e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2783524990081787s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.409385681152344e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.62939453125e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.951085090637207s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.4541759490966797s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0007021427154541016s
Extra | Recovery of all triples for STW Thesaurus for Economics took 40.75453448295593s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.257232904434204s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.5700011253356934s
Interoperability | New terms check for STW Thesaurus for Economics took 1.458247184753418s
Versatility | Languages check for STW Thesaurus for Economics took 1.578002691268921s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5015254020690918s
Security | Check HTTPS for STW Thesaurus for Economics took 0.16043543815612793s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.26853418350219727s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.25020647048950195s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.2806429862976074s
License | MR license check for STW Thesaurus for Economics took 0.2854018211364746s
License | HR license check for STW Thesaurus for Economics took 2.2677974700927734s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.29340052604675293s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6691346168518066s
Understandability | URI regex check for STW Thesaurus for Economics took 0.502241849899292s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.25290513038635254s
Verifiability | Authors check for STW Thesaurus for Economics took 0.26295900344848633s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.25624728202819824s
Performance | Throughput check for STW Thesaurus for Economics took 10.928922891616821s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7315735816955566s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2522120475769043s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.23241829872131348s
Interlinking | skos check for STW Thesaurus for Economics took 0.3098773956298828s
Interlinking | skos check for STW Thesaurus for Economics took 0.2848241329193115s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.24639558792114258s
Currency | Creation date check for STW Thesaurus for Economics took 0.5125131607055664s
Currency | Modification date check for STW Thesaurus for Economics took 0.5217580795288086s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 9.977545499801636s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.25984859466552734s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.23749899864196777s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.26339077949523926s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 11.191595077514648s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0451557636260986s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.3606674671173096s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.25496864318847656s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.4689123630523682s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.2916038036346436s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.225386381149292s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.2101590633392334s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6667499542236328s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.25973033905029297s
Security | Sign check for STW Thesaurus for Economics took 0.26493048667907715s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2007.5003769397736s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 1.561246395111084s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.021198511123657227s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00012373924255371094s
Believability | Calculation of trust value for STW Thesaurus for Economics took 8.106231689453125e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 2135.0903556346893s
Availability | SPARQL endpoint availability check for SudershanTech took 9.012222290039062e-05s
Availability | VoID file availability check for SudershanTech took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.2761714458465576s
Reputation | Calculation of the PageRank for SudershanTech took 0.02005910873413086s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.0279159545898438e-05s
Believability | Calculation of trust value for SudershanTech took 7.3909759521484375e-06s
INFO | --- Analysis for SudershanTech took 4.2044525146484375s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.5879840850830078s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.28589892387390137s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02033543586730957s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.744529724121094e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 8.106231689453125e-06s
INFO | --- Analysis for sudocfr took 7.945828437805176s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 0.990147590637207s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006425380706787109s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 311.95285749435425s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.6787490844726562s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.4174113273620605s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.9274704456329346s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 2.920877456665039s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.3356750011444092s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5491015911102295s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5560281276702881s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5397138595581055s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5734713077545166s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 8.219513654708862s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5870130062103271s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6749651432037354s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.0572352409362793s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.533768892288208s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5689716339111328s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.52457594871521s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.782768487930298s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 7.510185241699219e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5815558433532715s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5845322608947754s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6125152111053467s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5554835796356201s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5500669479370117s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.061450481414795s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.128685712814331s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 51.94902491569519s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5157427787780762s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5472252368927002s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5220456123352051s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 14.636967897415161s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.36179375648498535s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.562913179397583s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 13.711697816848755s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 10.0701584815979s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.4607217311859s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 4.138411045074463s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.0209567546844482s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.1952126026153564s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5587015151977539s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 1630.8667442798615s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.7080693244934082s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02205944061279297s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 0.0001552104949951172s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 5.4836273193359375e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 9.5367431640625e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 5432.421673774719s
Availability | SPARQL endpoint availability check for Surge Radio took 4.267692565917969e-05s
Availability | VoID file availability check for Surge Radio took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.6938376426696777s
Reputation | Calculation of the PageRank for Surge Radio took 0.020238876342773438s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.296966552734375e-05s
Believability | Calculation of trust value for Surge Radio took 8.58306884765625e-06s
INFO | --- Analysis for surge-radio took 5.217829942703247s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.1484832763671875e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.2603178024291992s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.0207674503326416s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.1948089599609375e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 7.3909759521484375e-06s
INFO | --- Analysis for SWAT took 40.828171253204346s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.291534423828125e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.41439127922058105s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2565422058105469s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020008325576782227s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.747245788574219e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 7.3909759521484375e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.523593425750732s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.0481219291687012s
Availability | VoID file availability check for SweFN-RDF took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.3859217166900635s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for SweFN-RDF took 7.3909759521484375e-06s
INFO | --- Analysis for swefn-rdf took 5.696751594543457s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.124641418457031e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2947969436645508s
Reputation | Calculation of the PageRank for SwetoDblp took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.4809112548828125e-05s
Believability | Calculation of trust value for SwetoDblp took 6.4373016357421875e-06s
INFO | --- Analysis for sweto-dblp took 22.750463008880615s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 4.653057813644409s
Availability | VoID file availability check for Swift Vocabulary took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.27747440338134766s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 6.723403930664062e-05s
Believability | Calculation of trust value for Swift Vocabulary took 9.059906005859375e-06s
INFO | --- Analysis for Swift took 9.23238468170166s
Availability | SPARQL endpoint availability check for SymbolicData took 4.00543212890625e-05s
Availability | VoID file availability check for SymbolicData took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.2503013610839844s
Reputation | Calculation of the PageRank for SymbolicData took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for SymbolicData took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 2.8371810913085938e-05s
Believability | Calculation of trust value for SymbolicData took 8.821487426757812e-06s
INFO | --- Analysis for symbolicdata took 2.8481979370117188s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.220008850097656e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0014226436614990234s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.2614445686340332s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020758867263793945s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.4809112548828125e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 8.821487426757812e-06s
INFO | --- Analysis for symptoms-in-chinese took 52.76518654823303s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.5132086277008057s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0006413459777832031s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.6417257785797119s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 1.000126838684082s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 50.292693853378296s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.86440134048462s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.19244670867919922s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 10.685891389846802s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.13160300254821777s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.4050145149230957s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.8355932235717773s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.21317577362060547s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.3128042221069336s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.789305448532104s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.494976282119751s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 34.8165009021759s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.4475064277648926s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.18355059623718262s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.5950818061828613s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.528874397277832s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.195324659347534s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.796287536621094e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.74637770652771s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.8757376670837402s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5728809833526611s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5486388206481934s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.457275629043579s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 1.7253336906433105s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 1.6807520389556885s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 63.72131395339966s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.22156810760498047s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2977311611175537s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.002744436264038086s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.002081155776977539s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.21224164962768555s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.37071752548218s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2575502395629883s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.4347138404846191s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.1697990894317627s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 46.030120611190796s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002173900604248047s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.32306861877441406s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.2202303409576416s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 22.587228059768677s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.8076627254486084s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 0.000141143798828125s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 7.867813110351562e-06s
INFO | --- Analysis for sztaki-lod took 482.75790643692017s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 5.555152893066406e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0003566741943359375s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.267749547958374s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 4.8160552978515625e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 8.106231689453125e-06s
INFO | --- Analysis for t4gm-info took 4.3302528858184814s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.124641418457031e-05s
Availability | VoID file availability check for tags2con delicious took 0.0008928775787353516s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.7884204387664795s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 5.173683166503906e-05s
Believability | Calculation of trust value for tags2con delicious took 6.67572021484375e-06s
INFO | --- Analysis for tags2con-delicious took 845.9714651107788s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 264.205863237381s
Availability | VoID file availability check for Taiwan geographic names took 0.0009195804595947266s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.281414270401001s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.8650970458984375e-05s
Believability | Calculation of trust value for Taiwan geographic names took 8.344650268554688e-06s
INFO | --- Analysis for taiwan-geographic-names took 668.1794855594635s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.220008850097656e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.2795145511627197s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.441375732421875e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 8.58306884765625e-06s
INFO | --- Analysis for talis-openlibrary took 4.362741470336914s
Availability | SPARQL endpoint availability check for TalkBank took 4.029273986816406e-05s
Availability | VoID file availability check for TalkBank took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for TalkBank took 0.27327561378479004s
Reputation | Calculation of the PageRank for TalkBank took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0008490085601806641s
Interlinking | Calculation of Clustering coefficient for TalkBank took 4.172325134277344e-05s
Believability | Calculation of trust value for TalkBank took 8.344650268554688e-06s
INFO | --- Analysis for talkbank took 3.7901034355163574s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9466357231140137s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.2683718204498291s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012135505676269531s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for taxonconcept took 14.210978269577026s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.1484832763671875e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.2623436450958252s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 7.82012939453125e-05s
Believability | Calculation of trust value for taxonconcept-assets took 7.867813110351562e-06s
INFO | --- Analysis for taxonconcept-assets took 3.247103214263916s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.1961669921875e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.26960039138793945s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020378589630126953s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.555152893066406e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 6.4373016357421875e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.7013237476348877s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.6327698230743408s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0009090900421142578s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.2621173858642578s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02008986473083496s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.792213439941406e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 7.3909759521484375e-06s
INFO | --- Analysis for taxref-ld took 5.46236777305603s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.6353688240051s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.7360236644744873s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02149510383605957s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.673004150390625e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.2636184692382812e-05s
INFO | --- Analysis for tcga took 540.7620716094971s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3470942974090576s
Availability | VoID file availability check for TCGA Roadmap took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.28528738021850586s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.534027099609375e-05s
Believability | Calculation of trust value for TCGA Roadmap took 7.867813110351562e-06s
INFO | --- Analysis for tcga-roadmap took 6.769089937210083s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.7853648662567139s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3119797706604004s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 9.870529174804688e-05s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.867813110351562e-06s
INFO | --- Analysis for tcmgenedit_dataset took 141.4540388584137s
Availability | SPARQL endpoint availability check for TDS took 4.1961669921875e-05s
Availability | VoID file availability check for TDS took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for TDS took 0.6941726207733154s
Reputation | Calculation of the PageRank for TDS took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for TDS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for TDS took 4.482269287109375e-05s
Believability | Calculation of trust value for TDS took 8.821487426757812e-06s
INFO | --- Analysis for tds took 5.5549352169036865s
Availability | SPARQL endpoint availability check for TED Talks took 4.00543212890625e-05s
Availability | VoID file availability check for TED Talks took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for TED Talks took 0.24479460716247559s
Reputation | Calculation of the PageRank for TED Talks took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for TED Talks took 3.0279159545898438e-05s
Believability | Calculation of trust value for TED Talks took 7.62939453125e-06s
INFO | --- Analysis for ted-talks took 2.8652567863464355s
Availability | SPARQL endpoint availability check for TEKORD took 4.7206878662109375e-05s
Availability | VoID file availability check for TEKORD took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2878570556640625s
Reputation | Calculation of the PageRank for TEKORD took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for TEKORD took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for TEKORD took 0.0008473396301269531s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.76837158203125e-05s
Believability | Calculation of trust value for TEKORD took 8.821487426757812e-06s
INFO | --- Analysis for tekord took 4.986245632171631s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 3.090167999267578s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.26052188873291016s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00012731552124023438s
Believability | Calculation of trust value for Telegraphis Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for telegraphis took 9.493094682693481s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 5.507469177246094e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.00122833251953125s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.2922368049621582s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.794929504394531e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 7.867813110351562e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.497252464294434s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.25782036781311035s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.02020549774169922s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 8.106231689453125e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.889669179916382s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.00543212890625e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.278118371963501s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for terminesp took 2.947901487350464s
Availability | SPARQL endpoint availability check for Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Ontology took 0.2821683883666992s
Reputation | Calculation of the PageRank for Ontology took 0.020375728607177734s
Interlinking | Calculation of Degree of Connection for Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Ontology took 2.7418136596679688e-05s
Believability | Calculation of trust value for Ontology took 6.67572021484375e-06s
INFO | --- Analysis for Terrorist_attack took 2.834852933883667s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.1961669921875e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.27278590202331543s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.337860107421875e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 7.62939453125e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.4488584995269775s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 3.933906555175781e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.265380859375s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 2.9325485229492188e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.3909759521484375e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.9450409412384033s
Availability | SPARQL endpoint availability check for Teseo took 7.176399230957031e-05s
Availability | VoID file availability check for Teseo took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Teseo took 0.2719919681549072s
Reputation | Calculation of the PageRank for Teseo took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Teseo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Teseo took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.0040740966796875e-05s
Believability | Calculation of trust value for Teseo took 7.152557373046875e-06s
INFO | --- Analysis for teseo took 2.982841968536377s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.1961669921875e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.25715136528015137s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 2.8371810913085938e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 7.152557373046875e-06s
INFO | --- Analysis for Tesla_Deaths took 3.9748246669769287s
Availability | SPARQL endpoint availability check for test took 8.034706115722656e-05s
Availability | VoID file availability check for test took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for test took 0.26843881607055664s
Reputation | Calculation of the PageRank for test took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for test took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for test took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for test took 3.0994415283203125e-05s
Believability | Calculation of trust value for test took 8.344650268554688e-06s
INFO | --- Analysis for test took 2.3636600971221924s
Availability | SPARQL endpoint availability check for Test took 4.267692565917969e-05s
Availability | VoID file availability check for Test took 0.0003387928009033203s
Completeness | Calculation of interlinking completeness for Test took 0.2600677013397217s
Reputation | Calculation of the PageRank for Test took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for Test took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Test took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Test took 2.9325485229492188e-05s
Believability | Calculation of trust value for Test took 8.106231689453125e-06s
INFO | --- Analysis for Test took 2.3330013751983643s
Availability | SPARQL endpoint availability check for test-svu took 20.1945583820343s
Availability | VoID file availability check for test-svu took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for test-svu took 0.25508642196655273s
Reputation | Calculation of the PageRank for test-svu took 0.021352052688598633s
Interlinking | Calculation of Degree of Connection for test-svu took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for test-svu took 5.1021575927734375e-05s
Believability | Calculation of trust value for test-svu took 9.059906005859375e-06s
INFO | --- Analysis for test-svu took 52.556098222732544s
Availability | SPARQL endpoint availability check for Test took 4.1961669921875e-05s
Availability | VoID file availability check for Test took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Test took 0.27915000915527344s
Reputation | Calculation of the PageRank for Test took 0.021030664443969727s
Interlinking | Calculation of Degree of Connection for Test took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Test took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Test took 3.0279159545898438e-05s
Believability | Calculation of trust value for Test took 5.9604644775390625e-06s
INFO | --- Analysis for Test_ took 2.411285161972046s
Availability | SPARQL endpoint availability check for xxxxx took 261.96696305274963s
Availability | VoID file availability check for xxxxx took 0.0008094310760498047s
Completeness | Calculation of interlinking completeness for xxxxx took 0.27532386779785156s
Reputation | Calculation of the PageRank for xxxxx took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for xxxxx took 0.00010204315185546875s
Believability | Calculation of trust value for xxxxx took 8.106231689453125e-06s
INFO | --- Analysis for testee took 797.0386440753937s
Availability | SPARQL endpoint availability check for Texai Lexicon took 6.866455078125e-05s
Availability | VoID file availability check for Texai Lexicon took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.2742891311645508s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020851850509643555s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.314018249511719e-05s
Believability | Calculation of trust value for Texai Lexicon took 9.298324584960938e-06s
INFO | --- Analysis for texai_lexicon took 3.1465933322906494s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.1484832763671875e-05s
Availability | VoID file availability check for tharawat magazine took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.2646138668060303s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for tharawat magazine took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010323524475097656s
Believability | Calculation of trust value for tharawat magazine took 7.3909759521484375e-06s
INFO | --- Analysis for tharawat-magazine-com took 3.0245182514190674s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.076957702636719e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.3083536624908447s
Reputation | Calculation of the PageRank for The CIARD RING took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 2.765655517578125e-05s
Believability | Calculation of trust value for The CIARD RING took 7.867813110351562e-06s
INFO | --- Analysis for the-ciard-ring took 3.0319466590881348s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.14699268341064453s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.2664201259613037s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 2.765655517578125e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 6.67572021484375e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.5993125438690186s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.9683895111083984s
Availability | VoID file availability check for The European Library Open Dataset took 0.0012416839599609375s
Extra | Recovery of all triples for The European Library Open Dataset took 1.3707759380340576s
Performance | Total latancy measurement for The European Library Open Dataset took 1.1933188438415527s
Amount of data | Number of triples check for The European Library Open Dataset took 30.216519117355347s
Versatility | Languages check for The European Library Open Dataset took 0.3373603820800781s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.198280572891235s
Interpretability | RDF structures check for The European Library Open Dataset took 0.3247194290161133s
Versatility | Serialization formats check for The European Library Open Dataset took 0.34711647033691406s
Availability | RDF dump link check for The European Library Open Dataset took 0.2414391040802002s
License | MR license check for The European Library Open Dataset took 1.2385740280151367s
License | HR license check for The European Library Open Dataset took 0.3110172748565674s
Amount of data | Number of property check for The European Library Open Dataset took 0.2246227264404297s
Understandability | Number of label check for The European Library Open Dataset took 3.3164379596710205s
Understandability | URI regex check for The European Library Open Dataset took 0.49410223960876465s
Understandability | Vocabs check for The European Library Open Dataset took 0.24521994590759277s
Verifiability | Authors check for The European Library Open Dataset took 0.24274063110351562s
Verifiability | Publishers check for The European Library Open Dataset took 0.2598600387573242s
Performance | Throughput check for The European Library Open Dataset took 11.721999168395996s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.009506225585938e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.2058403491973877s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.2844200134277344s
Interlinking | skos check for The European Library Open Dataset took 1.019759178161621s
Interlinking | skos check for The European Library Open Dataset took 0.28141212463378906s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.21879005432128906s
Currency | Creation date check for The European Library Open Dataset took 3.299438714981079s
Currency | Modification date check for The European Library Open Dataset took 1.1448514461517334s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.509862422943115s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.23706912994384766s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.362530469894409s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.03197622299194336s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02763962745666504s
Consistency | Disjoint class check for The European Library Open Dataset took 0.23310136795043945s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.46647024154663s
Consistency | Misplaced classes for The European Library Open Dataset took 0.35652923583984375s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.7303898334503174s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.1807951927185059s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.418845891952515s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03467845916748047s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.28496742248535156s
Security | Sign check for The European Library Open Dataset took 0.2740952968597412s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 4.945483446121216s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.326993465423584s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.842613220214844e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 7.867813110351562e-06s
INFO | --- Analysis for the-european-library-open-dataset took 403.88141417503357s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.04519462585449s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.7376515865325928s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.021040678024291992s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010609626770019531s
Believability | Calculation of trust value for The Eurostat Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for the-eurostat-linked-data took 244.07462072372437s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.9577484130859375e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.2716329097747803s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 2.8371810913085938e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.62939453125e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 2.9000308513641357s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.124641418457031e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.00041937828063964844s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2911093235015869s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.081031799316406e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 6.67572021484375e-06s
INFO | --- Analysis for the-living-lod-cloud took 42.050071477890015s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 3.933906555175781e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.25771546363830566s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.0279159545898438e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 7.867813110351562e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.346036434173584s
Availability | SPARQL endpoint availability check for The View From took 0.07914566993713379s
Availability | VoID file availability check for The View From took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for The View From took 0.27727413177490234s
Reputation | Calculation of the PageRank for The View From took 0.020958423614501953s
Interlinking | Calculation of Degree of Connection for The View From took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for The View From took 8.535385131835938e-05s
Believability | Calculation of trust value for The View From took 8.106231689453125e-06s
INFO | --- Analysis for the-view-from took 2.9666478633880615s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.436063766479492s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.27426671981811523s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.765655517578125e-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.1010148525238s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.14176297187805s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.29206252098083496s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020334243774414062s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 5.650520324707031e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 7.3909759521484375e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 102.66804146766663s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.291534423828125e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.26044487953186035s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00011110305786132812s
Believability | Calculation of trust value for The Content Wrangler took 8.821487426757812e-06s
INFO | --- Analysis for thecontentwrangler-com took 2.9342830181121826s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.124641418457031e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2772691249847412s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.24249267578125e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 8.106231689453125e-06s
INFO | --- Analysis for thesaurus-bncf took 3.3398971557617188s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.3392181396484375e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2801234722137451s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.147125244140625e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 8.58306884765625e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.5929579734802246s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.4734039306640625s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.30146241188049316s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.343292236328125e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 8.344650268554688e-06s
INFO | --- Analysis for thesaurus-w took 4.58697247505188s
Availability | SPARQL endpoint availability check for theses.fr took 6.961822509765625e-05s
Availability | VoID file availability check for theses.fr took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for theses.fr took 0.25880002975463867s
Reputation | Calculation of the PageRank for theses.fr took 0.0219419002532959s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0009417533874511719s
Interlinking | Calculation of Clustering coefficient for theses.fr took 6.031990051269531e-05s
Believability | Calculation of trust value for theses.fr took 9.059906005859375e-06s
INFO | --- Analysis for thesesfr took 4.591557741165161s
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.00027370452880859375s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.2616121768951416s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.021129369735717773s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.7670135498046875e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 8.58306884765625e-06s
INFO | --- Analysis for Thinkphile took 2.317355155944824s
Availability | SPARQL endpoint availability check for ThIST took 265.4326367378235s
Availability | VoID file availability check for ThIST took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for ThIST took 0.29081249237060547s
Reputation | Calculation of the PageRank for ThIST took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for ThIST took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.131431579589844e-05s
Believability | Calculation of trust value for ThIST took 8.821487426757812e-06s
INFO | --- Analysis for thist took 564.5740694999695s
Availability | SPARQL endpoint availability check for TIP took 40.03690958023071s
Availability | VoID file availability check for TIP took 0.0003230571746826172s
Completeness | Calculation of interlinking completeness for TIP took 0.28943967819213867s
Reputation | Calculation of the PageRank for TIP took 0.02085089683532715s
Interlinking | Calculation of Degree of Connection for TIP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TIP took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010943412780761719s
Believability | Calculation of trust value for TIP took 7.62939453125e-06s
INFO | --- Analysis for tip took 105.21751046180725s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.220008850097656e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0003981590270996094s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.2486894130706787s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.021083593368530273s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 2.9325485229492188e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 6.4373016357421875e-06s
INFO | --- Analysis for TOPMODEL took 23.14234471321106s
Availability | SPARQL endpoint availability check for Tourpedia took 4.2438507080078125e-05s
Availability | VoID file availability check for Tourpedia took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.6973130702972412s
Reputation | Calculation of the PageRank for Tourpedia took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 2.9802322387695312e-05s
Believability | Calculation of trust value for Tourpedia took 8.58306884765625e-06s
INFO | --- Analysis for tourpedia took 5.515368938446045s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.3990485668182373s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.25087904930114746s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.021150588989257812s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0008323192596435547s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 4.100799560546875e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 7.62939453125e-06s
INFO | --- Analysis for TP-data took 8.043094158172607s
Availability | SPARQL endpoint availability check for True Parents Legacy Teaching Archive took 4.3392181396484375e-05s
Availability | VoID file availability check for True Parents Legacy Teaching Archive took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for True Parents Legacy Teaching Archive took 0.2780308723449707s
Reputation | Calculation of the PageRank for True Parents Legacy Teaching Archive took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for True Parents Legacy Teaching Archive took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for True Parents Legacy Teaching Archive took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for True Parents Legacy Teaching Archive took 1.2874603271484375e-05s
Believability | Calculation of trust value for True Parents Legacy Teaching Archive took 7.62939453125e-06s
INFO | --- Analysis for tplegacy took 4.569180965423584s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 2.1666207313537598s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.000713348388671875s
Extra | Recovery of all triples for Trackloaded Linked Open Data took 2.669146776199341s
Performance | Total latancy measurement for Trackloaded Linked Open Data took 5.165814399719238s
Amount of data | Number of triples check for Trackloaded Linked Open Data took 1.6931328773498535s
Interoperability | New terms check for Trackloaded Linked Open Data took 2.8241145610809326s
Versatility | Languages check for Trackloaded Linked Open Data took 1.8170421123504639s
Interpretability | Number of blank nodes check for Trackloaded Linked Open Data took 1.934272050857544s
Interpretability | RDF structures check for Trackloaded Linked Open Data took 1.9407031536102295s
Versatility | Serialization formats check for Trackloaded Linked Open Data took 1.8157267570495605s
Availability | RDF dump link check for Trackloaded Linked Open Data took 1.802121639251709s
License | MR license check for Trackloaded Linked Open Data took 1.7316501140594482s
License | HR license check for Trackloaded Linked Open Data took 2.911283254623413s
Amount of data | Number of property check for Trackloaded Linked Open Data took 2.2329368591308594s
Understandability | Number of label check for Trackloaded Linked Open Data took 1.973266839981079s
Understandability | URI regex check for Trackloaded Linked Open Data took 4.2169835567474365s
Understandability | Vocabs check for Trackloaded Linked Open Data took 1.680652141571045s
Verifiability | Authors check for Trackloaded Linked Open Data took 1.8717601299285889s
Verifiability | Publishers check for Trackloaded Linked Open Data took 1.8263678550720215s
Performance | Throughput check for Trackloaded Linked Open Data took 12.894210815429688s
Amount of data | Check the number of entities for Trackloaded Linked Open Data took 7.104873657226562e-05s
Verifiability | Contribs. check for Trackloaded Linked Open Data took 1.7843904495239258s
Interlinking | sameAs chians check for Trackloaded Linked Open Data took 1.6902995109558105s
Interlinking | skos check for Trackloaded Linked Open Data took 1.6663062572479248s
Interlinking | skos check for Trackloaded Linked Open Data took 1.1702935695648193s
Timeliness | dataset update frequency check for Trackloaded Linked Open Data took 1.8637933731079102s
Currency | Creation date check for Trackloaded Linked Open Data took 3.5728676319122314s
Currency | Modification date check for Trackloaded Linked Open Data took 4.136333227157593s
Rep.Conc. | URIs length for Trackloaded Linked Open Data took 3.3760313987731934s
Interoperability | New vocabularies check for Trackloaded Linked Open Data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Linked Open Data took 1.8732144832611084s
Consistency | Disjoint class check for Trackloaded Linked Open Data took 1.6386325359344482s
Consistency | Check Misplaced properties for Trackloaded Linked Open Data took 3.315030336380005s
Consistency | Check Ontology hijacking for Trackloaded Linked Open Data took 0.6318514347076416s
Consistency | Check Invalid usage of undefined properties for Trackloaded Linked Open Data took 1.7663545608520508s
Conciseness | Check Extensional conciseness for Trackloaded Linked Open Data took 0.00016164779663085938s
Security | Sign check for Trackloaded Linked Open Data took 0.6989948749542236s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.2997112274169922s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.1920928955078125e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Linked Open Data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for trackloaded took 121.59444236755371s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.9207184314727783s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.26578855514526367s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.020247220993041992s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.291534423828125e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 7.867813110351562e-06s
INFO | --- Analysis for traditional-korean-medicine took 6.3430421352386475s
Availability | SPARQL endpoint availability check for Traffic Scotland took 10.137758493423462s
Availability | VoID file availability check for Traffic Scotland took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.26569414138793945s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020378589630126953s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.4809112548828125e-05s
Believability | Calculation of trust value for Traffic Scotland took 6.198883056640625e-06s
INFO | --- Analysis for traffic-scotland took 13.031225204467773s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.18874144554138184s
Availability | VoID file availability check for Transparency International Linked Data took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2904198169708252s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.020445823669433594s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010752677917480469s
Believability | Calculation of trust value for Transparency International Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for transparency-linked-data took 3.1622743606567383s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.718217134475708s
Availability | VoID file availability check for transport.data.gov.uk took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.26339221000671387s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.107589721679688e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 6.67572021484375e-06s
INFO | --- Analysis for transport-data-gov-uk took 4.08256983757019s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 4.792213439941406e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.28603124618530273s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 3.0517578125e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 8.58306884765625e-06s
INFO | --- Analysis for transport-openuplabs took 2.950413227081299s
Availability | SPARQL endpoint availability check for Trelios took 4.267692565917969e-05s
Availability | VoID file availability check for Trelios took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Trelios took 0.2788827419281006s
Reputation | Calculation of the PageRank for Trelios took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for Trelios took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.1205673217773438e-05s
Believability | Calculation of trust value for Trelios took 8.58306884765625e-06s
INFO | --- Analysis for Trelios took 2.413666009902954s
Availability | SPARQL endpoint availability check for Twarql took 10.59297490119934s
Availability | VoID file availability check for Twarql took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Twarql took 0.2794804573059082s
Reputation | Calculation of the PageRank for Twarql took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Twarql took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.961822509765625e-05s
Believability | Calculation of trust value for Twarql took 7.867813110351562e-06s
INFO | --- Analysis for twarql took 13.092822790145874s
Availability | SPARQL endpoint availability check for TWC Data-gov took 8.869171142578125e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.2580699920654297s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.0994415283203125e-05s
Believability | Calculation of trust value for TWC Data-gov took 6.4373016357421875e-06s
INFO | --- Analysis for twc-data-gov took 2.526087999343872s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 5.745887756347656e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.2879502773284912s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.02085256576538086s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 2.9802322387695312e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 9.059906005859375e-06s
INFO | --- Analysis for twc-demos took 3.447021007537842s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.15469145774841309s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007293224334716797s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.4054086208343506s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.218650817871094e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 5.9604644775390625e-06s
INFO | --- Analysis for twc-healthdata took 15.539092540740967s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 5.431595087051392s
Availability | VoID file availability check for Instance Hub (all) took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.33443784713745117s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02694559097290039s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.001369476318359375s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 0.00011086463928222656s
Believability | Calculation of trust value for Instance Hub (all) took 8.106231689453125e-06s
INFO | --- Analysis for twc-hub took 67.78861904144287s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.13799309730529785s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.32613062858581543s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010752677917480469s
Believability | Calculation of trust value for IEEE VIS Source Data took 7.3909759521484375e-06s
INFO | --- Analysis for twc-ieeevis took 119.4233820438385s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.1961669921875e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.2573120594024658s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.96453857421875e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 5.245208740234375e-06s
INFO | --- Analysis for twc-logd took 2.4415199756622314s
Availability | SPARQL endpoint availability check for twc-opendap took 0.12628984451293945s
Availability | VoID file availability check for twc-opendap took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.25984883308410645s
Reputation | Calculation of the PageRank for twc-opendap took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 6.628036499023438e-05s
Believability | Calculation of trust value for twc-opendap took 7.867813110351562e-06s
INFO | --- Analysis for twc-opendap took 61.18521213531494s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 4.00543212890625e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.27732229232788086s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 2.9325485229492188e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 7.867813110351562e-06s
INFO | --- Analysis for tweetskb took 2.9245076179504395s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 3.9577484130859375e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.2679586410522461s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 4.1484832763671875e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 8.58306884765625e-06s
INFO | --- Analysis for twitter-lids took 2.9851250648498535s
Availability | SPARQL endpoint availability check for typepad took 4.839897155761719e-05s
Availability | VoID file availability check for typepad took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for typepad took 0.26461362838745117s
Reputation | Calculation of the PageRank for typepad took 0.020275354385375977s
Interlinking | Calculation of Degree of Connection for typepad took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for typepad took 4.982948303222656e-05s
Believability | Calculation of trust value for typepad took 8.344650268554688e-06s
INFO | --- Analysis for typepad took 3.022393226623535s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.968454122543335s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.26766085624694824s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 3.9577484130859375e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 7.152557373046875e-06s
INFO | --- Analysis for ub-mannheim-linked-data took 4.802780866622925s
Availability | SPARQL endpoint availability check for Uberblic.org took 0.10616040229797363s
Availability | VoID file availability check for Uberblic.org took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.2797696590423584s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010323524475097656s
Believability | Calculation of trust value for Uberblic.org took 8.821487426757812e-06s
INFO | --- Analysis for uberblic took 2.8757660388946533s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6476950645446777s
Availability | VoID file availability check for UDante in LiLa took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.27991676330566406s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for UDante in LiLa took 8.821487426757812e-06s
INFO | --- Analysis for UDante took 4.087883710861206s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.8219192028045654s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.2900245189666748s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 8.344650268554688e-06s
INFO | --- Analysis for ufo took 4.367597341537476s
Availability | SPARQL endpoint availability check for Uganda Disasters took 6.0558319091796875e-05s
Availability | VoID file availability check for Uganda Disasters took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.27789735794067383s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 5.1975250244140625e-05s
Believability | Calculation of trust value for Uganda Disasters took 7.152557373046875e-06s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.49186110496521s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.14923691749572754s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.25373411178588867s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.0001010894775390625s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for uis-linked-data took 2.5744080543518066s
Availability | SPARQL endpoint availability check for UK Legislation took 4.267692565917969e-05s
Availability | VoID file availability check for UK Legislation took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.27122998237609863s
Reputation | Calculation of the PageRank for UK Legislation took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.702278137207031e-05s
Believability | Calculation of trust value for UK Legislation took 6.198883056640625e-06s
INFO | --- Analysis for uk-legislation-api took 3.3786492347717285s
Availability | SPARQL endpoint availability check for UK Postcodes took 7.939338684082031e-05s
Availability | VoID file availability check for UK Postcodes took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.27626800537109375s
Reputation | Calculation of the PageRank for UK Postcodes took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 6.008148193359375e-05s
Believability | Calculation of trust value for UK Postcodes took 7.3909759521484375e-06s
INFO | --- Analysis for uk-postcodes took 2.84336256980896s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.172325134277344e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.25268054008483887s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.021106719970703125s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0008637905120849609s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00012993812561035156s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 8.106231689453125e-06s
INFO | --- Analysis for umbel took 5.101315259933472s
Availability | SPARQL endpoint availability check for UMTHES took 4.076957702636719e-05s
Availability | VoID file availability check for UMTHES took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for UMTHES took 0.28290772438049316s
Reputation | Calculation of the PageRank for UMTHES took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for UMTHES took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for UMTHES took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.00543212890625e-05s
Believability | Calculation of trust value for UMTHES took 4.76837158203125e-06s
INFO | --- Analysis for umthes took 3.741037368774414s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.8412449359893799s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.2583339214324951s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.0517578125e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 5.7220458984375e-06s
INFO | --- Analysis for un-hazardous-numbers took 9.371668338775635s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 5.3882598876953125e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2564389705657959s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020350933074951172s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for unesco-thesaurus took 2.928663969039917s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 3.9577484130859375e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.26219677925109863s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for unescothes took 2.840357780456543s
Availability | SPARQL endpoint availability check for UniProt took 1.361924648284912s
Availability | VoID file availability check for UniProt took 0.0006215572357177734s
Extra | Recovery of all triples for UniProt took 76.96136593818665s
Performance | Total latancy measurement for UniProt took 2.576829671859741s
Amount of data | Number of triples check for UniProt took 0.1654980182647705s
Interoperability | New terms check for UniProt took 1.400376558303833s
Versatility | Languages check for UniProt took 300.10194420814514s
Interpretability | Number of blank nodes check for UniProt took 0.4679090976715088s
Interpretability | RDF structures check for UniProt took 0.15522265434265137s
Versatility | Serialization formats check for UniProt took 0.11609792709350586s
Availability | RDF dump link check for UniProt took 0.10308480262756348s
License | MR license check for UniProt took 0.1052103042602539s
License | HR license check for UniProt took 300.06223034858704s
Amount of data | Number of property check for UniProt took 0.15875458717346191s
Understandability | Number of label check for UniProt took 44.8760449886322s
Understandability | URI regex check for UniProt took 0.19988012313842773s
Understandability | Vocabs check for UniProt took 0.08968138694763184s
Verifiability | Authors check for UniProt took 0.08689546585083008s
Verifiability | Publishers check for UniProt took 0.10692501068115234s
Performance | Throughput check for UniProt took 14.644348621368408s
Amount of data | Check the number of entities for UniProt took 7.05718994140625e-05s
Verifiability | Contribs. check for UniProt took 0.09079790115356445s
Interlinking | sameAs chians check for UniProt took 0.09347057342529297s
Interlinking | skos check for UniProt took 0.2261204719543457s
Interlinking | skos check for UniProt took 0.09136056900024414s
Timeliness | dataset update frequency check for UniProt took 0.0954279899597168s
Currency | Creation date check for UniProt took 0.22552132606506348s
Currency | Modification date check for UniProt took 0.17549848556518555s
Rep.Conc. | URIs length for UniProt took 158.50170397758484s
Interoperability | New vocabularies check for UniProt took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.09018945693969727s
Accuracy | Check Functional Property for UniProt took 0.09053897857666016s
Accuracy | Check Inverse Functional Property for UniProt took 0.07850790023803711s
Accuracy | Check Empty annotation labels for UniProt took 23.247062921524048s
Accuracy | Check White space in annotation for UniProt took 2.523231267929077s
Accuracy | Check Datatype consistency for UniProt took 7.123688697814941s
Consistency | Disjoint class check for UniProt took 0.09461522102355957s
Consistency | Check Misplaced properties for UniProt took 11.943510055541992s
Consistency | Check Ontology hijacking for UniProt took 28.640284776687622s
Consistency | Check Invalid usage of undefined classes for UniProt took 19377.82272028923s
Consistency | Check Invalid usage of undefined properties for UniProt took 4.724764585494995s
Conciseness | Check Extensional conciseness for UniProt took 12.562724351882935s
Conciseness | Check Intensional conciseness for UniProt took 0.20860862731933594s
Security | Sign check for UniProt took 0.13405537605285645s
Availability | Check URIs Dereferenciability for UniProt took 5.9658119678497314s
Completeness | Calculation of interlinking completeness for UniProt took 1.8315799236297607s
Reputation | Calculation of the PageRank for UniProt took 0.6112582683563232s
Interlinking | Calculation of Degree of Connection for UniProt took 0.010687589645385742s
Interlinking | Calculation of Centrality for UniProt took 0.008032560348510742s
Interlinking | Calculation of Clustering coefficient for UniProt took 0.005587577819824219s
Interoperability | Check the re-using of existing vocabs for UniProt took 7.152557373046875e-06s
Believability | Calculation of trust value for UniProt took 1.4543533325195312e-05s
INFO | --- Analysis for UniProt took 20812.833827495575s
Availability | SPARQL endpoint availability check for UniProt took 1.3121287822723389s
Availability | VoID file availability check for UniProt took 0.00060272216796875s
Extra | Recovery of all triples for UniProt took 78.06056690216064s
Performance | Total latancy measurement for UniProt took 3.4510459899902344s
Amount of data | Number of triples check for UniProt took 0.3832743167877197s
Versatility | Languages check for UniProt took 300.31204748153687s
Interpretability | Number of blank nodes check for UniProt took 0.5783390998840332s
Security | Check HTTPS for UniProt took 1.3769876956939697s
Interpretability | RDF structures check for UniProt took 0.1568894386291504s
Versatility | Serialization formats check for UniProt took 0.1929309368133545s
Availability | RDF dump link check for UniProt took 0.16955351829528809s
License | MR license check for UniProt took 0.15970730781555176s
License | HR license check for UniProt took 0.18211817741394043s
Amount of data | Number of property check for UniProt took 0.18421459197998047s
Understandability | Number of label check for UniProt took 0.17512011528015137s
Understandability | URI regex check for UniProt took 0.33264780044555664s
Understandability | Vocabs check for UniProt took 0.1605367660522461s
Verifiability | Authors check for UniProt took 0.20456743240356445s
Verifiability | Publishers check for UniProt took 0.17319726943969727s
Performance | Throughput check for UniProt took 19.080461978912354s
Amount of data | Check the number of entities for UniProt took 0.0002415180206298828s
Verifiability | Contribs. check for UniProt took 0.15623164176940918s
Interlinking | sameAs chians check for UniProt took 0.18329811096191406s
Interlinking | skos check for UniProt took 0.17348504066467285s
Interlinking | skos check for UniProt took 0.1474471092224121s
Timeliness | dataset update frequency check for UniProt took 0.18630385398864746s
Currency | Creation date check for UniProt took 0.34721875190734863s
Currency | Modification date check for UniProt took 0.3513522148132324s
Rep.Conc. | URIs length for UniProt took 161.27421689033508s
Interoperability | New vocabularies check for UniProt took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.15890169143676758s
Accuracy | Check Datatype consistency for UniProt took 7.120335340499878s
Consistency | Disjoint class check for UniProt took 0.17000484466552734s
Consistency | Check Ontology hijacking for UniProt took 0.17124342918395996s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.545405387878418s
Conciseness | Check Extensional conciseness for UniProt took 2.691261053085327s
Security | Sign check for UniProt took 0.16303253173828125s
Availability | Check URIs Dereferenciability for UniProt took 3.9257054328918457s
Completeness | Calculation of interlinking completeness for UniProt took 0.8646080493927002s
Reputation | Calculation of the PageRank for UniProt took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for UniProt took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.604194641113281e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 9.5367431640625e-07s
Believability | Calculation of trust value for UniProt took 8.106231689453125e-06s
INFO | --- Analysis for uniprot took 1120.164184331894s
Availability | SPARQL endpoint availability check for UniProt citations took 4.4345855712890625e-05s
Availability | VoID file availability check for UniProt citations took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.26125359535217285s
Reputation | Calculation of the PageRank for UniProt citations took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.147125244140625e-05s
Believability | Calculation of trust value for UniProt citations took 7.62939453125e-06s
INFO | --- Analysis for uniprot-citations took 4.596564292907715s
Availability | SPARQL endpoint availability check for UniProt databases took 4.57763671875e-05s
Availability | VoID file availability check for UniProt databases took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.2501559257507324s
Reputation | Calculation of the PageRank for UniProt databases took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 3.0517578125e-05s
Believability | Calculation of trust value for UniProt databases took 7.62939453125e-06s
INFO | --- Analysis for uniprot-databases took 4.592266798019409s
Availability | SPARQL endpoint availability check for uniprot-metadata took 4.458427429199219e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0011725425720214844s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.26627516746520996s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.127357482910156e-05s
Believability | Calculation of trust value for uniprot-metadata took 7.3909759521484375e-06s
INFO | --- Analysis for uniprot-metadata took 3.787409782409668s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 4.1961669921875e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.2682523727416992s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020255327224731445s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 2.956390380859375e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 9.298324584960938e-06s
INFO | --- Analysis for uniprot-taxonomy took 3.6070556640625s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.076957702636719e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.262345552444458s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.0279159545898438e-05s
Believability | Calculation of trust value for UniProt UniParc took 8.106231689453125e-06s
INFO | --- Analysis for uniprot-uniparc took 2.9144444465637207s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.124641418457031e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.2534608840942383s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.02199864387512207s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0011456012725830078s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 4.553794860839844e-05s
Believability | Calculation of trust value for UniProt UniPathway took 8.344650268554688e-06s
INFO | --- Analysis for uniprot-unipathway took 2.8434996604919434s
Availability | SPARQL endpoint availability check for UniProtKB took 1.8643879890441895s
Availability | VoID file availability check for UniProtKB took 0.0005924701690673828s
Extra | Recovery of all triples for UniProtKB took 86.86716771125793s
Performance | Total latancy measurement for UniProtKB took 2.7864551544189453s
Amount of data | Number of triples check for UniProtKB took 0.18334436416625977s
Interoperability | New terms check for UniProtKB took 1.4362788200378418s
Versatility | Languages check for UniProtKB took 300.06598591804504s
Interpretability | Number of blank nodes check for UniProtKB took 0.49317431449890137s
Interpretability | RDF structures check for UniProtKB took 0.20937800407409668s
Versatility | Serialization formats check for UniProtKB took 0.10717177391052246s
Availability | RDF dump link check for UniProtKB took 0.09243941307067871s
License | MR license check for UniProtKB took 0.12270760536193848s
License | HR license check for UniProtKB took 300.1213319301605s
Amount of data | Number of property check for UniProtKB took 0.16998791694641113s
Understandability | Number of label check for UniProtKB took 40.97183346748352s
Understandability | URI regex check for UniProtKB took 0.16368770599365234s
Understandability | Vocabs check for UniProtKB took 0.0982363224029541s
Verifiability | Authors check for UniProtKB took 0.1262199878692627s
Verifiability | Publishers check for UniProtKB took 0.10381793975830078s
Performance | Throughput check for UniProtKB took 13.448232173919678s
Amount of data | Check the number of entities for UniProtKB took 7.319450378417969e-05s
Verifiability | Contribs. check for UniProtKB took 0.09187006950378418s
Interlinking | sameAs chians check for UniProtKB took 0.13439488410949707s
Interlinking | skos check for UniProtKB took 0.14567208290100098s
Interlinking | skos check for UniProtKB took 0.08417153358459473s
Timeliness | dataset update frequency check for UniProtKB took 0.08385276794433594s
Currency | Creation date check for UniProtKB took 0.18275666236877441s
Currency | Modification date check for UniProtKB took 0.2377622127532959s
Rep.Conc. | URIs length for UniProtKB took 154.70746517181396s
Interoperability | New vocabularies check for UniProtKB took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.07910990715026855s
Accuracy | Check Functional Property for UniProtKB took 0.14197683334350586s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.10246443748474121s
Accuracy | Check Empty annotation labels for UniProtKB took 28.84411072731018s
Accuracy | Check White space in annotation for UniProtKB took 2.518540382385254s
Accuracy | Check Datatype consistency for UniProtKB took 7.143644094467163s
Consistency | Disjoint class check for UniProtKB took 0.08071517944335938s
Consistency | Check Misplaced properties for UniProtKB took 11.961260557174683s
Consistency | Check Ontology hijacking for UniProtKB took 32.05581212043762s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 19222.750761270523s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 1.6152732372283936s
Conciseness | Check Extensional conciseness for UniProtKB took 2.6482787132263184s
Conciseness | Check Intensional conciseness for UniProtKB took 0.3516218662261963s
Security | Sign check for UniProtKB took 0.07985830307006836s
Availability | Check URIs Dereferenciability for UniProtKB took 4.341960191726685s
Completeness | Calculation of interlinking completeness for UniProtKB took 1.6719026565551758s
Reputation | Calculation of the PageRank for UniProtKB took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for UniProtKB took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 1.6689300537109375e-06s
Believability | Calculation of trust value for UniProtKB took 9.059906005859375e-06s
INFO | --- Analysis for uniprotkb took 20796.504721403122s
Availability | SPARQL endpoint availability check for UniProt UniRef took 4.291534423828125e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.2561988830566406s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.020902395248413086s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 3.719329833984375e-05s
Believability | Calculation of trust value for UniProt UniRef took 8.821487426757812e-06s
INFO | --- Analysis for uniref took 4.578322887420654s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 4.0531158447265625e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.26005101203918457s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 3.266334533691406e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 8.58306884765625e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 3.6979763507843018s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 4.482269287109375e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.2594940662384033s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.266334533691406e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 6.4373016357421875e-06s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 3.312081813812256s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0007524490356445312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.2598686218261719s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.830527305603027s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.26277685165405273s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 3.4471778869628906s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.34923481941223145s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.309279680252075s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.27636265754699707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.245557069778442s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.27707862854003906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.180758714675903s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007846355438232422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.2622945308685303s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.021199703216552734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 0.00011754035949707031s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.102102518081665s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.27713513374328613s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.866058826446533s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 5.340576171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.25944995880126953s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.019938230514526367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.077903032302856s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.27489781379699707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.02016901969909668s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.195473194122314s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.2681419849395752s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020198822021484375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.15502119064331s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.2648496627807617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020131826400756836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.42769169807434s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.27371835708618164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.499305963516235s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2844727039337158s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 3.848510503768921s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.284318208694458s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.19674563407898s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 5.4836273193359375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0007648468017578125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.25945281982421875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 12.906580924987793s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.2557861804962158s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.12055230140686s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0009548664093017578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.2867774963378906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.034036874771118s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.26340770721435547s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 12.888003587722778s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 5.316734313964844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.2583651542663574s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0008590221405029297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.040990352630615s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0003943443298339844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.2499375343322754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.0047385692596436s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2630882263183594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 12.939900159835815s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2708017826080322s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.220750093460083s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.3108642101287842s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.22344446182251s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.2652592658996582s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.02009415626525879s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 3.170967102050781e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.379373073577881s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.2694427967071533s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 3.699939489364624s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.26194238662719727s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 3.8460943698883057s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.2722499370574951s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 3.513054609298706s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.26892805099487305s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.21655559539795s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 6.651878356933594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.26271891593933105s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.02021646499633789s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.092050790786743s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.25931429862976074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 3.573773145675659s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.2759835720062256s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.354875564575195s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.26236701011657715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020025968551635742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 3.7910425662994385s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.2653188705444336s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020329952239990234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.103190422058105s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.25803565979003906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.105747699737549s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.2650446891784668s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.019970417022705078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 3.428229808807373s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.696846008300781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.2610175609588623s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 6.031990051269531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.185132503509521s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.2582364082336426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 3.5412089824676514s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.2592020034790039s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02010941505432129s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.066955804824829s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.27090883255004883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 12.985182762145996s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.26658058166503906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.18283724784851s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0007643699645996094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.2715315818786621s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020062923431396484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.006802558898926s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.76837158203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.27373433113098145s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.127424478530884s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.26950669288635254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-persian took 3.545663595199585s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.2843348979949951s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.02015233039855957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.257250785827637s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 5.5789947509765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.253673791885376s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 12.713113784790039s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0007860660552978516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2665536403656006s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020190954208374023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.040121078491211s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 6.794929504394531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.26487302780151367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.147432804107666s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.252138614654541s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020753860473632812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.13155722618103s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.2691323757171631s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020142078399658203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.145042896270752s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.27547502517700195s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.3077471256256104s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.26357412338256836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.13225531578064s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 7.414817810058594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.2837333679199219s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.16891098022461s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.24752140045166016s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.19119119644165s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.27002787590026855s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.001157999038696s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.26436781883239746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.302422523498535s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0008242130279541016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.25525426864624023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.02028965950012207s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 12.869633197784424s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.2747228145599365s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02167034149169922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0010890960693359375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 3.531078338623047s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.27741551399230957s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.345785617828369s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007684230804443359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.3761777877807617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020380735397338867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.364620685577393s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.25757360458374023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.178804874420166s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 7.319450378417969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.26813244819641113s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.270451068878174s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0008444786071777344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.25505924224853516s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.744529724121094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.052435398101807s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2810652256011963s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 5.5789947509765625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.263023853302002s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.27983713150024414s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.02006077766418457s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.090013265609741s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.649162292480469e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.26446104049682617s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.723403930664062e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 7.867813110351562e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.459296941757202s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 4.0531158447265625e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.269589900970459s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 8.821487426757812e-06s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 2.973079204559326s
Availability | SPARQL endpoint availability check for University of Bristol took 4.076957702636719e-05s
Availability | VoID file availability check for University of Bristol took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.2607917785644531s
Reputation | Calculation of the PageRank for University of Bristol took 0.021114110946655273s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.24249267578125e-05s
Believability | Calculation of trust value for University of Bristol took 8.344650268554688e-06s
INFO | --- Analysis for university-of-bristol took 2.869417905807495s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 5.626678466796875e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2711005210876465s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.9114227294921875e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 7.3909759521484375e-06s
INFO | --- Analysis for university-plymouth-reading-lists took 3.0232341289520264s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.291534423828125e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.2656383514404297s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.528594970703125e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 7.867813110351562e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.7656822204589844s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 4.46251916885376s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2792332172393799s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 6.842613220214844e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 7.867813110351562e-06s
INFO | --- Analysis for unodc took 11.700551509857178s
Availability | SPARQL endpoint availability check for Super Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Super Ontology took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2603287696838379s
Reputation | Calculation of the PageRank for Super Ontology took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 7.987022399902344e-05s
Believability | Calculation of trust value for Super Ontology took 8.344650268554688e-06s
INFO | --- Analysis for upper-ontology took 3.7061967849731445s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 0.508697509765625s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.2711770534515381s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.600120544433594e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Upper_Ontology took 4.364376544952393s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 4.744529724121094e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.2589685916900635s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.170967102050781e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 7.867813110351562e-06s
INFO | --- Analysis for Urban_Atlas_ took 2.300971269607544s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.6205692291259766s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0002765655517578125s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 133.43472862243652s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 0.9484784603118896s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.125691890716553s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.167468786239624s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.17444348335266s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.733105421066284s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.23815488815307617s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 12.6105215549469s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.29998183250427246s
License | MR license check for Urban Atlas dataset @PSNC took 0.5456981658935547s
License | HR license check for Urban Atlas dataset @PSNC took 300.2443172931671s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.534677267074585s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 2.52120041847229s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 0.6231491565704346s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.451946496963501s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.19489622116088867s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.2561635971069336s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.453055381774902s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 8.726119995117188e-05s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.1777198314666748s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.20865845680236816s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.5462346076965332s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.4390537738800049s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 6.104821443557739s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.5165600776672363s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.21558070182800293s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 165.774888753891s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.1972815990447998s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.2937638759613037s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.29480433464050293s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 37.38431930541992s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.6911590099334717s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.655081272125244s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.20915007591247559s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 95.35847234725952s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.465301990509033s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 41.64932060241699s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.3028945922851562s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 93.07612228393555s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.749342441558838s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.6415910720825195s
Security | Sign check for Urban Atlas dataset @PSNC took 0.8823049068450928s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 18.58540964126587s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.5682032108306885s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.021263599395751953s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 4.76837158203125e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 2326.900574684143s
Availability | SPARQL endpoint availability check for URIBurner took 0.6370742321014404s
Availability | VoID file availability check for URIBurner took 0.0003921985626220703s
Extra | Recovery of all triples for URIBurner took 122.28838634490967s
Performance | Total latancy measurement for URIBurner took 1.1514942646026611s
Amount of data | Number of triples check for URIBurner took 3.91050124168396s
Interoperability | New terms check for URIBurner took 42.639835596084595s
Versatility | Languages check for URIBurner took 122.35311937332153s
Interpretability | Number of blank nodes check for URIBurner took 2.243962049484253s
Security | Check HTTPS for URIBurner took 0.28103041648864746s
Interpretability | RDF structures check for URIBurner took 1.8566672801971436s
Versatility | Serialization formats check for URIBurner took 7.234524965286255s
Availability | RDF dump link check for URIBurner took 20.460814714431763s
License | MR license check for URIBurner took 9.392268180847168s
License | HR license check for URIBurner took 125.64995408058167s
Amount of data | Number of property check for URIBurner took 16.958786249160767s
Understandability | Number of label check for URIBurner took 53.76494383811951s
Understandability | URI regex check for URIBurner took 38.14431667327881s
Understandability | Vocabs check for URIBurner took 13.361577272415161s
Verifiability | Authors check for URIBurner took 11.180448770523071s
Verifiability | Publishers check for URIBurner took 24.782063007354736s
Performance | Throughput check for URIBurner took 154.0037546157837s
Amount of data | Check the number of entities for URIBurner took 9.179115295410156e-05s
Verifiability | Contribs. check for URIBurner took 22.835749864578247s
Interlinking | sameAs chians check for URIBurner took 20.960090160369873s
Interlinking | skos check for URIBurner took 23.41020631790161s
Interlinking | skos check for URIBurner took 18.989558935165405s
Timeliness | dataset update frequency check for URIBurner took 24.984841346740723s
Currency | Creation date check for URIBurner took 110.76810789108276s
Currency | Modification date check for URIBurner took 21.93563961982727s
Rep.Conc. | URIs length for URIBurner took 275.70301842689514s
Consistency | Deprecated classes/propertiers check for URIBurner took 12.690579891204834s
Accuracy | Check Functional Property for URIBurner took 6.768198013305664s
Accuracy | Check Inverse Functional Property for URIBurner took 8.73037338256836s
Consistency | Disjoint class check for URIBurner took 8.497548341751099s
Consistency | Check Ontology hijacking for URIBurner took 138.12520098686218s
Consistency | Check Invalid usage of undefined properties for URIBurner took 143.70228791236877s
Conciseness | Check Extensional conciseness for URIBurner took 0.0007007122039794922s
Security | Sign check for URIBurner took 18.564826011657715s
Completeness | Calculation of interlinking completeness for URIBurner took 1.6231141090393066s
Reputation | Calculation of the PageRank for URIBurner took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.799003601074219e-05s
Believability | Calculation of trust value for URIBurner took 6.67572021484375e-06s
INFO | --- Analysis for uriburner took 8026.908091545105s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.506111145019531e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2593705654144287s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.9802322387695312e-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 urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 4.012382507324219s
Availability | SPARQL endpoint availability check for Legija Stranaca took 4.1484832763671875e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.2588977813720703s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.020233154296875s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.0994415283203125e-05s
Believability | Calculation of trust value for Legija Stranaca took 6.4373016357421875e-06s
INFO | --- Analysis for Uros_Legija_Susa took 3.2678585052490234s
Availability | SPARQL endpoint availability check for Legija took 4.2438507080078125e-05s
Availability | VoID file availability check for Legija took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Legija took 0.6997668743133545s
Reputation | Calculation of the PageRank for Legija took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Legija took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Legija took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for Legija took 3.3855438232421875e-05s
Believability | Calculation of trust value for Legija took 7.867813110351562e-06s
INFO | --- Analysis for Uros_Susa took 2.7454159259796143s
Availability | SPARQL endpoint availability check for US Political Violence took 5.5789947509765625e-05s
Availability | VoID file availability check for US Political Violence took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.27138543128967285s
Reputation | Calculation of the PageRank for US Political Violence took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for US Political Violence took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.0279159545898438e-05s
Believability | Calculation of trust value for US Political Violence took 7.867813110351562e-06s
INFO | --- Analysis for us-political-violence took 3.2738702297210693s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.8238110542297363s
Availability | VoID file availability check for USAGE review corpus took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.2595033645629883s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.1948089599609375e-05s
Believability | Calculation of trust value for USAGE review corpus took 7.62939453125e-06s
INFO | --- Analysis for usage-review-corpus took 4.015607833862305s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 3.2048211097717285s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.25992298126220703s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.414817810058594e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for utpl-lod took 7.79454779624939s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.100799560546875e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.2867765426635742s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 3.266334533691406e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 7.3909759521484375e-06s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.953455924987793s
Availability | SPARQL endpoint availability check for terrorist attack took 4.100799560546875e-05s
Availability | VoID file availability check for terrorist attack took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.24656915664672852s
Reputation | Calculation of the PageRank for terrorist attack took 0.020396709442138672s
Interlinking | Calculation of Degree of Connection for terrorist attack took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.0517578125e-05s
Believability | Calculation of trust value for terrorist attack took 7.3909759521484375e-06s
INFO | --- Analysis for varsha took 4.057268142700195s
Availability | SPARQL endpoint availability check for VA took 4.267692565917969e-05s
Availability | VoID file availability check for VA took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for VA took 0.24895763397216797s
Reputation | Calculation of the PageRank for VA took 0.020925283432006836s
Interlinking | Calculation of Degree of Connection for VA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VA took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for VA took 3.0517578125e-05s
Believability | Calculation of trust value for VA took 8.106231689453125e-06s
INFO | --- Analysis for Vehicule_Autonome took 2.6276185512542725s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.6190211772918701s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.28501391410827637s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.020348548889160156s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for VelezIndexTotiusArtis took 3.871509313583374s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 1.040649652481079s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2714805603027344s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0009984970092773438s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 0.00010466575622558594s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 9.298324584960938e-06s
INFO | --- Analysis for verrijktkoninkrijk took 10.30452299118042s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.220008850097656e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.27504873275756836s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017070770263671875s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 8.58306884765625e-06s
INFO | --- Analysis for viaf took 3.044349431991577s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 4.172325134277344e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.282015323638916s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 9.059906005859375e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 2.8660683631896973s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.2438507080078125e-05s
Availability | VoID file availability check for Vihar Exports took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.2619473934173584s
Reputation | Calculation of the PageRank for Vihar Exports took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 2.956390380859375e-05s
Believability | Calculation of trust value for Vihar Exports took 8.821487426757812e-06s
INFO | --- Analysis for Vihar_Exports took 2.278089761734009s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 4.100799560546875e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.2724125385284424s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.020083189010620117s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 2.9802322387695312e-05s
Believability | Calculation of trust value for vimeo.videoobject took 7.62939453125e-06s
INFO | --- Analysis for vimeo_videoobject took 2.9273555278778076s
Availability | SPARQL endpoint availability check for VIVO took 4.220008850097656e-05s
Availability | VoID file availability check for VIVO took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for VIVO took 0.26843786239624023s
Reputation | Calculation of the PageRank for VIVO took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.771087646484375e-05s
Believability | Calculation of trust value for VIVO took 7.3909759521484375e-06s
INFO | --- Analysis for vivo took 5.637972354888916s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.27411794662475586s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.02020883560180664s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.082389831542969e-05s
Believability | Calculation of trust value for VIVO Cornell took 7.867813110351562e-06s
INFO | --- Analysis for vivo-cornell-university took 5.590716600418091s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 4.00543212890625e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.27271246910095215s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.020348310470581055s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 3.1948089599609375e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 6.67572021484375e-06s
INFO | --- Analysis for vivo-cu-boulder took 2.854619264602661s
Availability | SPARQL endpoint availability check for VIVO Indiana took 5.316734313964844e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2744419574737549s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.020251035690307617s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 7.82012939453125e-05s
Believability | Calculation of trust value for VIVO Indiana took 7.3909759521484375e-06s
INFO | --- Analysis for vivo-indiana-university took 2.991431713104248s
Availability | SPARQL endpoint availability check for VIVO Ponce took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.2687501907348633s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0009632110595703125s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.7670135498046875e-05s
Believability | Calculation of trust value for VIVO Ponce took 7.152557373046875e-06s
INFO | --- Analysis for vivo-ponce took 2.789091110229492s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 7.200241088867188e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.26959657669067383s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.021004199981689453s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.6716461181640625e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 6.9141387939453125e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 2.740718364715576s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 5.626678466796875e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.25369882583618164s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.322166442871094e-05s
Believability | Calculation of trust value for VIVO University of Florida took 8.344650268554688e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.5418314933776855s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.172325134277344e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.2894866466522217s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.886222839355469e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 7.62939453125e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.7647340297698975s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.315376281738281e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.27981066703796387s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020975112915039062s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.838539123535156e-05s
Believability | Calculation of trust value for VIVO WUSTL took 7.867813110351562e-06s
INFO | --- Analysis for vivo-wustl took 2.764699697494507s
Availability | SPARQL endpoint availability check for vivo2doi took 7.081031799316406e-05s
Availability | VoID file availability check for vivo2doi took 0.0007352828979492188s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.2572212219238281s
Reputation | Calculation of the PageRank for vivo2doi took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.696846008300781e-05s
Believability | Calculation of trust value for vivo2doi took 8.106231689453125e-06s
INFO | --- Analysis for vivo2doi took 25.996614694595337s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.3392181396484375e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.2758646011352539s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020647287368774414s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.842613220214844e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 7.867813110351562e-06s
INFO | --- Analysis for vu-wordnet took 16.751204252243042s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.06718897819519043s
Availability | VoID file availability check for vulnerapedia took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.277111291885376s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.699562072753906e-05s
Believability | Calculation of trust value for vulnerapedia took 8.344650268554688e-06s
INFO | --- Analysis for vulnerapedia took 2.9065439701080322s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 7.915496826171875e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0003762245178222656s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.25649428367614746s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2636184692382812e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 7.867813110351562e-06s
INFO | --- Analysis for VVASIAK took 2.321824789047241s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 4.38690185546875e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.25968098640441895s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.075599670410156e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 7.867813110351562e-06s
INFO | --- Analysis for Vyvasta took 2.3300883769989014s
Availability | SPARQL endpoint availability check for W3C took 4.3392181396484375e-05s
Availability | VoID file availability check for W3C took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for W3C took 0.2662065029144287s
Reputation | Calculation of the PageRank for W3C took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for W3C took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00013780593872070312s
Believability | Calculation of trust value for W3C took 7.152557373046875e-06s
INFO | --- Analysis for w3c took 2.5287113189697266s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.124641418457031e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.27162599563598633s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.0517578125e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 1.7642974853515625e-05s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.9714856147766113s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.363059997558594e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0008018016815185547s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.2504885196685791s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00012445449829101562s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 8.58306884765625e-06s
INFO | --- Analysis for w3c-wordnet took 3.0379045009613037s
Availability | SPARQL endpoint availability check for WarSampo took 0.39742016792297363s
Availability | VoID file availability check for WarSampo took 0.0007424354553222656s
Extra | Recovery of all triples for WarSampo took 146.26318097114563s
Performance | Total latancy measurement for WarSampo took 0.8214833736419678s
Amount of data | Number of triples check for WarSampo took 20.94160556793213s
Interoperability | New terms check for WarSampo took 3.735349178314209s
Versatility | Languages check for WarSampo took 58.22613739967346s
Interpretability | Number of blank nodes check for WarSampo took 18.966248035430908s
Security | Check HTTPS for WarSampo took 0.3738727569580078s
Interpretability | RDF structures check for WarSampo took 0.1930980682373047s
Versatility | Serialization formats check for WarSampo took 0.19362163543701172s
Availability | RDF dump link check for WarSampo took 0.9853622913360596s
License | MR license check for WarSampo took 0.18383240699768066s
License | HR license check for WarSampo took 49.32197117805481s
Amount of data | Number of property check for WarSampo took 0.17727375030517578s
Understandability | Number of label check for WarSampo took 9.45396637916565s
Understandability | URI regex check for WarSampo took 0.33373379707336426s
Understandability | Vocabs check for WarSampo took 0.16051769256591797s
Verifiability | Authors check for WarSampo took 0.18065166473388672s
Verifiability | Publishers check for WarSampo took 0.17416834831237793s
Performance | Throughput check for WarSampo took 10.488933801651001s
Amount of data | Check the number of entities for WarSampo took 15.233173370361328s
Verifiability | Contribs. check for WarSampo took 0.1914691925048828s
Interlinking | sameAs chians check for WarSampo took 0.19082093238830566s
Interlinking | skos check for WarSampo took 0.20182323455810547s
Interlinking | skos check for WarSampo took 0.1545414924621582s
Timeliness | dataset update frequency check for WarSampo took 0.15388846397399902s
Currency | Creation date check for WarSampo took 0.351259708404541s
Currency | Modification date check for WarSampo took 0.3462822437286377s
Rep.Conc. | URIs length for WarSampo took 91.59985494613647s
Interoperability | New vocabularies check for WarSampo took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.18216252326965332s
Accuracy | Check Functional Property for WarSampo took 0.18864178657531738s
Accuracy | Check Inverse Functional Property for WarSampo took 0.1539618968963623s
Accuracy | Check Empty annotation labels for WarSampo took 50.81889605522156s
Accuracy | Check White space in annotation for WarSampo took 2.1868510246276855s
Accuracy | Check Datatype consistency for WarSampo took 5.247073650360107s
Consistency | Disjoint class check for WarSampo took 0.198347806930542s
Consistency | Check Misplaced properties for WarSampo took 21.08324408531189s
Consistency | Check Ontology hijacking for WarSampo took 56.55297660827637s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.2235164642333984s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.4443402290344238s
Conciseness | Check Extensional conciseness for WarSampo took 2.8017728328704834s
Conciseness | Check Intensional conciseness for WarSampo took 0.2598702907562256s
Security | Sign check for WarSampo took 0.16700220108032227s
Availability | Check URIs Dereferenciability for WarSampo took 2.6211276054382324s
Completeness | Calculation of interlinking completeness for WarSampo took 0.9383194446563721s
Reputation | Calculation of the PageRank for WarSampo took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for WarSampo took 9.179115295410156e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.6689300537109375e-06s
Believability | Calculation of trust value for WarSampo took 6.9141387939453125e-06s
INFO | --- Analysis for warsampo took 1276.1299493312836s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 21.320024490356445s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.26943302154541016s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02008819580078125s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 8.0108642578125e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for wasabi took 56.863211154937744s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.6508369445800781s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.00023436546325683594s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 123.53987765312195s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.9312269687652588s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 10.098458766937256s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 13.815305471420288s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.15307807922363s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.5035791397094727s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.24408817291259766s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 12.705908060073853s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.3068521022796631s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.6281061172485352s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.1814875602722s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.4946415424346924s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 2.7878034114837646s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 0.7725808620452881s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.4367218017578125s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.2178659439086914s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.2583036422729492s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.248741626739502s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 8.416175842285156e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.17718029022216797s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.19495010375976562s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4557065963745117s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.42617130279541016s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 6.164358139038086s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.5249922275543213s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.2426002025604248s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 169.42370700836182s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.211991548538208s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.32643651962280273s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.33545589447021484s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 41.16896343231201s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.6622278690338135s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.675386905670166s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.21103215217590332s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 90.00611400604248s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.435856819152832s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 33.82114219665527s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.21480131149292s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 82.41173958778381s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.760305643081665s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.5569961071014404s
Security | Sign check for FAO water areas classification as linked data @PSNC took 0.6511454582214355s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 18.6710422039032s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 1.3693923950195312s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 5.412101745605469e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 3.0279159545898438e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 8.821487426757812e-06s
INFO | --- Analysis for Water_Areas_Classification took 2305.258568048477s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.1968679428100586s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00026679039001464844s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 123.49409079551697s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.9482848644256592s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 8.665345430374146s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 20.2172954082489s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.2162458896637s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 3.119962215423584s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.24230432510375977s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 10.198089838027954s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.26450562477111816s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.4896690845489502s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.241854429245s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.29565978050231934s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 2.9972376823425293s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 0.8330841064453125s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.4181861877441406s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.2035510540008545s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.24347209930419922s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.417211055755615s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 0.00011324882507324219s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.18094873428344727s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.19487547874450684s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4407041072845459s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.46863746643066406s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 7.395788908004761s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.4756300449371338s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.23041439056396484s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 171.31519532203674s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.20426344871520996s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.2658717632293701s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.26978397369384766s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 45.107072591781616s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.6800639629364014s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.6574251651763916s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.21280574798583984s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 92.75847506523132s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.455375909805298s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 37.78406643867493s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.252335786819458s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 89.52886199951172s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.7975289821624756s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5592012405395508s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 0.7921097278594971s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 18.514511108398438s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 1.0436155796051025s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 3.981590270996094e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Water_Buffer took 2328.220920085907s
