Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.601478576660156e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0007352828979492188s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.6972296237945557s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.654240608215332s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00037932395935058594s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 8.344650268554688e-06s
INFO | --- Analysis for 0080-3626 took 7.659373760223389s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.482269287109375e-05s
Availability | VoID file availability check for 土地利用图 took 0.0003349781036376953s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.2685580253601074s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.00102996826171875s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.7670135498046875e-05s
Believability | Calculation of trust value for 土地利用图 took 1.2874603271484375e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.817734956741333s
Availability | SPARQL endpoint availability check for 113322 took 4.601478576660156e-05s
Availability | VoID file availability check for 113322 took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for 113322 took 0.27686023712158203s
Reputation | Calculation of the PageRank for 113322 took 0.0201108455657959s
Interlinking | Calculation of Degree of Connection for 113322 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.600120544433594e-05s
Believability | Calculation of trust value for 113322 took 8.58306884765625e-06s
INFO | --- Analysis for 11 took 4.198902130126953s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.2438507080078125e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2404308319091797s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020335674285888672s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.075599670410156e-05s
Believability | Calculation of trust value for Korepetycje Buki took 8.106231689453125e-06s
INFO | --- Analysis for 12323 took 2.7676501274108887s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06307101249694824s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2785940170288086s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020181894302368164s
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.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.678436279296875e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 6.67572021484375e-06s
INFO | --- Analysis for 2000-us-census-rdf took 2.5449554920196533s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.478224992752075s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2980070114135742s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020155906677246094s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.029273986816406e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 4.76837158203125e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.605700254440308s
Availability | SPARQL endpoint availability check for Open Data Web took 0.10886001586914062s
Availability | VoID file availability check for Open Data Web took 0.000244140625s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2702956199645996s
Reputation | Calculation of the PageRank for Open Data Web took 0.02006697654724121s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.1948089599609375e-05s
Believability | Calculation of trust value for Open Data Web took 6.4373016357421875e-06s
INFO | --- Analysis for _data.odw.tw took 2.594982624053955s
Availability | SPARQL endpoint availability check for 土地利用 took 4.363059997558594e-05s
Availability | VoID file availability check for 土地利用 took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.25716137886047363s
Reputation | Calculation of the PageRank for 土地利用 took 0.020013093948364258s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.6941299438476562e-05s
Believability | Calculation of trust value for 土地利用 took 6.4373016357421875e-06s
INFO | --- Analysis for _data1.odw.tw took 2.401289701461792s
Availability | SPARQL endpoint availability check for 土地利用模型 took 7.033348083496094e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2914927005767822s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.170967102050781e-05s
Believability | Calculation of trust value for 土地利用模型 took 7.3909759521484375e-06s
INFO | --- Analysis for _data2.odw.tw took 4.099358320236206s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.2438507080078125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2729196548461914s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8848648071289062e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.7819576263427734s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.363059997558594e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0007841587066650391s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2833402156829834s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02015376091003418s
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.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.0517578125e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 7.62939453125e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 27.579687356948853s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 7.104873657226562e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0003478527069091797s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.24969768524169922s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.0201416015625s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.0279159545898438e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 5.0067901611328125e-06s
INFO | --- Analysis for A1 took 2.8214385509490967s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.9200267791748047s
Availability | VoID file availability check for SummerOlympics took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.25844287872314453s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020128965377807617s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 7.843971252441406e-05s
Believability | Calculation of trust value for SummerOlympics took 5.9604644775390625e-06s
INFO | --- Analysis for abc took 7.166172742843628s
Availability | SPARQL endpoint availability check for Test_m took 4.291534423828125e-05s
Availability | VoID file availability check for Test_m took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Test_m took 0.2683556079864502s
Reputation | Calculation of the PageRank for Test_m took 0.02017951011657715s
Interlinking | Calculation of Degree of Connection for Test_m took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.0279159545898438e-05s
Believability | Calculation of trust value for Test_m took 7.152557373046875e-06s
INFO | --- Analysis for ABC took 2.32783842086792s
Availability | SPARQL endpoint availability check for my intro took 4.220008850097656e-05s
Availability | VoID file availability check for my intro took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for my intro took 0.24370241165161133s
Reputation | Calculation of the PageRank for my intro took 0.020172119140625s
Interlinking | Calculation of Degree of Connection for my intro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for my intro took 2.765655517578125e-05s
Believability | Calculation of trust value for my intro took 7.62939453125e-06s
INFO | --- Analysis for abhay_intro took 2.351691246032715s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.3611259460449219s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.25329160690307617s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020112991333007812s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.942054748535156e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for abs-linked-data took 2.725776433944702s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 5.984306335449219e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.2712545394897461s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.6464462280273438e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 7.3909759521484375e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.927720069885254s
Availability | SPARQL endpoint availability check for AcadOnto took 4.220008850097656e-05s
Availability | VoID file availability check for AcadOnto took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.27575087547302246s
Reputation | Calculation of the PageRank for AcadOnto took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.123283386230469e-05s
Believability | Calculation of trust value for AcadOnto took 6.9141387939453125e-06s
INFO | --- Analysis for acadonto took 4.147746562957764s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.350058317184448s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2583649158477783s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020186662673950195s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.695487976074219e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.76837158203125e-06s
INFO | --- Analysis for acorn-sat took 35.75542759895325s
Availability | SPARQL endpoint availability check for Addgene took 4.267692565917969e-05s
Availability | VoID file availability check for Addgene took 0.0008375644683837891s
Completeness | Calculation of interlinking completeness for Addgene took 0.25243258476257324s
Reputation | Calculation of the PageRank for Addgene took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Addgene took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.600120544433594e-05s
Believability | Calculation of trust value for Addgene took 7.867813110351562e-06s
INFO | --- Analysis for addgene took 16.329782009124756s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.315376281738281e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.25098586082458496s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.369850158691406e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 7.152557373046875e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 4.971264123916626s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.5727367401123047s
Availability | VoID file availability check for AEMET metereological dataset took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.25689172744750977s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.7670135498046875e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 6.198883056640625e-06s
INFO | --- Analysis for aemet took 5.262826204299927s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.124641418457031e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.25399136543273926s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02018427848815918s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.075599670410156e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 8.58306884765625e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.931994915008545s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03807997703552246s
Availability | VoID file availability check for AgriNepalData took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.27241945266723633s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020093679428100586s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.532669067382812e-05s
Believability | Calculation of trust value for AgriNepalData took 1.2874603271484375e-05s
INFO | --- Analysis for agrinepaldata took 2.4884989261627197s
Availability | SPARQL endpoint availability check for AGRIS took 261.73524165153503s
Availability | VoID file availability check for AGRIS took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for AGRIS took 0.27031660079956055s
Reputation | Calculation of the PageRank for AGRIS took 0.020396709442138672s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.557868957519531e-05s
Believability | Calculation of trust value for AGRIS took 6.198883056640625e-06s
INFO | --- Analysis for agris took 554.8976128101349s
Availability | SPARQL endpoint availability check for AGROVOC took 0.2144482135772705s
Availability | VoID file availability check for AGROVOC took 0.0006172657012939453s
Extra | Recovery of all triples for AGROVOC took 30.87323522567749s
Performance | Total latancy measurement for AGROVOC took 0.41341567039489746s
Amount of data | Number of triples check for AGROVOC took 16.6924729347229s
Interoperability | New terms check for AGROVOC took 2.7414262294769287s
Versatility | Languages check for AGROVOC took 30.08605194091797s
Interpretability | Number of blank nodes check for AGROVOC took 30.122615337371826s
Interpretability | RDF structures check for AGROVOC took 0.08874249458312988s
Versatility | Serialization formats check for AGROVOC took 0.1005558967590332s
Availability | RDF dump link check for AGROVOC took 0.10036969184875488s
License | MR license check for AGROVOC took 0.08131694793701172s
License | HR license check for AGROVOC took 0.4558591842651367s
Amount of data | Number of property check for AGROVOC took 0.11271524429321289s
Understandability | Number of label check for AGROVOC took 30.086488485336304s
Understandability | URI regex check for AGROVOC took 0.18511080741882324s
Understandability | Vocabs check for AGROVOC took 0.10246014595031738s
Verifiability | Authors check for AGROVOC took 0.09932494163513184s
Verifiability | Publishers check for AGROVOC took 0.10504293441772461s
Performance | Throughput check for AGROVOC took 10.539705514907837s
Amount of data | Check the number of entities for AGROVOC took 9.655952453613281e-05s
Verifiability | Contribs. check for AGROVOC took 0.17578411102294922s
Interlinking | sameAs chians check for AGROVOC took 0.1843557357788086s
Interlinking | skos check for AGROVOC took 0.17386293411254883s
Interlinking | skos check for AGROVOC took 0.17353034019470215s
Timeliness | dataset update frequency check for AGROVOC took 0.18930816650390625s
Currency | Creation date check for AGROVOC took 0.26087164878845215s
Currency | Modification date check for AGROVOC took 0.19132328033447266s
Rep.Conc. | URIs length for AGROVOC took 43.559566259384155s
Interoperability | New vocabularies check for AGROVOC took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08719205856323242s
Accuracy | Check Functional Property for AGROVOC took 0.07712411880493164s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.08861684799194336s
Accuracy | Check Empty annotation labels for AGROVOC took 23.17957043647766s
Accuracy | Check White space in annotation for AGROVOC took 2.991938829421997s
Consistency | Disjoint class check for AGROVOC took 0.08645939826965332s
Consistency | Check Misplaced properties for AGROVOC took 12.961227893829346s
Consistency | Check Ontology hijacking for AGROVOC took 30.628443479537964s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 11.495494365692139s
Conciseness | Check Extensional conciseness for AGROVOC took 0.0001552104949951172s
Conciseness | Check Intensional conciseness for AGROVOC took 0.09241867065429688s
Security | Sign check for AGROVOC took 0.10439443588256836s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7820019721984863s
Reputation | Calculation of the PageRank for AGROVOC took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011110305786132812s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.9073486328125e-06s
Believability | Calculation of trust value for AGROVOC took 7.62939453125e-06s
INFO | --- Analysis for agrovoc took 354.0891547203064s
Availability | SPARQL endpoint availability check for AGROVOC took 4.291534423828125e-05s
Availability | VoID file availability check for AGROVOC took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.8186550140380859s
Reputation | Calculation of the PageRank for AGROVOC took 0.0201873779296875s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.9604644775390625e-05s
Believability | Calculation of trust value for AGROVOC took 8.58306884765625e-06s
INFO | --- Analysis for agrovoc-skos took 4.380441904067993s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 0.893930196762085s
Availability | VoID file availability check for Analytics India Magazine took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.2614576816558838s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.8623809814453125e-05s
Believability | Calculation of trust value for Analytics India Magazine took 6.9141387939453125e-06s
INFO | --- Analysis for AIM took 5.3828394412994385s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 6.723403930664062e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.2712740898132324s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020077228546142578s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.7418136596679688e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 6.9141387939453125e-06s
INFO | --- Analysis for AISHE took 2.8656907081604004s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for  equipment ontology took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.28313326835632324s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02172112464904785s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for  equipment ontology took 8.821487426757812e-06s
INFO | --- Analysis for akash took 2.3789055347442627s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.124641418457031e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.2854609489440918s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 7.867813110351562e-06s
INFO | --- Analysis for aksworg took 2.9250848293304443s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.124641418457031e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.26575493812561035s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020023822784423828s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.8848648071289062e-05s
Believability | Calculation of trust value for AlchemyAPI took 7.867813110351562e-06s
INFO | --- Analysis for alchemyapi took 2.9595954418182373s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.0531158447265625e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.26174497604370117s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.0994415283203125e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 6.9141387939453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.916017770767212s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.1496760845184326s
Availability | VoID file availability check for aliada-scanbit-net took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.25649142265319824s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.019959688186645508s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00010752677917480469s
Believability | Calculation of trust value for aliada-scanbit-net took 7.62939453125e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.575159788131714s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.506111145019531e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.24882292747497559s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.147125244140625e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 1.2159347534179688e-05s
INFO | --- Analysis for allen-brain-atlas took 2.9516501426696777s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.4143743515014648s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006895065307617188s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 557.9219589233398s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 2.5843427181243896s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0526864528656s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 10.054627656936646s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 10.000888347625732s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 10.001007795333862s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 10.004396200180054s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 9.99801254272461s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 9.999118328094482s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 10.001046419143677s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 10.00181770324707s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 19.99736976623535s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 10.004452228546143s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 10.09919810295105s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 10.098782777786255s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 9.226799011230469e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 10.003180742263794s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 3.7563624382019043s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 10.048108339309692s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 10.093997716903687s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 9.999844074249268s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 20.00460648536682s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 20.097225189208984s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 25.295828580856323s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 10.00633978843689s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.674098491668701s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 10.020543813705444s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 21.434799432754517s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 10.133033990859985s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 131.91441679000854s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.2828059196472168s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.313138723373413s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7355639934539795s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 10.006973028182983s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12.511837720870972s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.980449914932251s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.019975900650024414s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 4.76837158203125e-07s
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 1592.532996892929s
Availability | SPARQL endpoint availability check for Alojamientos took 4.220008850097656e-05s
Availability | VoID file availability check for Alojamientos took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.2849137783050537s
Reputation | Calculation of the PageRank for Alojamientos took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 2.8133392333984375e-05s
Believability | Calculation of trust value for Alojamientos took 7.152557373046875e-06s
INFO | --- Analysis for alojamientos-zaragoza took 4.282476186752319s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.29070329666137695s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.26221704483032227s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.01996159553527832s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.5762786865234375e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 7.152557373046875e-06s
INFO | --- Analysis for alpino-rdf took 5.36850380897522s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.267692565917969e-05s
Availability | VoID file availability check for AAT-atawil took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.26970386505126953s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020032882690429688s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.0040740966796875e-05s
Believability | Calculation of trust value for AAT-atawil took 6.9141387939453125e-06s
INFO | --- Analysis for Altawil took 2.367037773132324s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.100799560546875e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0003437995910644531s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.2550039291381836s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020076990127563477s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.0279159545898438e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 6.9141387939453125e-06s
INFO | --- Analysis for am-collections-online took 2.9179670810699463s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.1484832763671875e-05s
Availability | VoID file availability check for Amer Nejma took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.2604947090148926s
Reputation | Calculation of the PageRank for Amer Nejma took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 2.9325485229492188e-05s
Believability | Calculation of trust value for Amer Nejma took 1.1444091796875e-05s
INFO | --- Analysis for Amer_Nejma took 2.401639461517334s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.2706723213195801s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 7.867813110351562e-06s
INFO | --- Analysis for amon took 2.9553513526916504s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.683218240737915s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2598080635070801s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020021677017211914s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.012222290039062e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 7.3909759521484375e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.732943534851074s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 5.316734313964844e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.28704190254211426s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.0279159545898438e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 6.9141387939453125e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.9062869548797607s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.267692565917969e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.28493666648864746s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02013230323791504s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 2.9802322387695312e-05s
Believability | Calculation of trust value for Animal Diversity Web took 6.9141387939453125e-06s
INFO | --- Analysis for animal-diversity-web took 2.9155139923095703s
Availability | SPARQL endpoint availability check for Anime Dataset took 8.20159912109375e-05s
Availability | VoID file availability check for Anime Dataset took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.249525785446167s
Reputation | Calculation of the PageRank for Anime Dataset took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.266334533691406e-05s
Believability | Calculation of trust value for Anime Dataset took 6.67572021484375e-06s
INFO | --- Analysis for Anime took 3.957153081893921s
Availability | SPARQL endpoint availability check for ANNO took 4.315376281738281e-05s
Availability | VoID file availability check for ANNO took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for ANNO took 0.259136438369751s
Reputation | Calculation of the PageRank for ANNO took 0.020151853561401367s
Interlinking | Calculation of Degree of Connection for ANNO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.4332275390625e-05s
Believability | Calculation of trust value for ANNO took 6.9141387939453125e-06s
INFO | --- Analysis for anno took 8.202675819396973s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.3392181396484375e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2555115222930908s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020104646682739258s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 8.940696716308594e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 6.9141387939453125e-06s
INFO | --- Analysis for AntiqueCarsCollection took 4.294461011886597s
Availability | SPARQL endpoint availability check for apache took 7.367134094238281e-05s
Availability | VoID file availability check for apache took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for apache took 0.27063465118408203s
Reputation | Calculation of the PageRank for apache took 0.020227432250976562s
Interlinking | Calculation of Degree of Connection for apache took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for apache took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for apache took 5.3882598876953125e-05s
Believability | Calculation of trust value for apache took 7.867813110351562e-06s
INFO | --- Analysis for apache took 3.3619418144226074s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.285320520401001s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020025968551635742s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf took 5.1601481437683105s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0008368492126464844s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2993342876434326s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020064353942871094s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.076957702636719e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.718883275985718s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.25997304916381836s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 5.14984130859375e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.55697774887085s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 5.2928924560546875e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2918574810028076s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.501317739486694s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2714686393737793s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020510435104370117s
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.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.9114227294921875e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.5673582553863525s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2806251049041748s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020139217376708984s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.520766735076904s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.24252986907958984s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020186901092529297s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.5268261432647705s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.25713086128234863s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020239591598510742s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.551228046417236s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2713010311126709s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.0200653076171875s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.609896183013916s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2723104953765869s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020155668258666992s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.634164810180664s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.24209165573120117s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.0202484130859375s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.505743741989136s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007610321044921875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.2759275436401367s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020164012908935547s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 25.568326473236084s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.9591064453125e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.26789259910583496s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020311355590820312s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 5.625993013381958s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.2687106132507324s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020245075225830078s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.61280369758606s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.7206878662109375e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2601025104522705s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02015519142150879s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.627415418624878s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2649383544921875s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02006053924560547s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.595563650131226s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2649819850921631s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 5.599929332733154s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2714354991912842s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020131826400756836s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.769906282424927s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.26228857040405273s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020172119140625s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007166862487792969s
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 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.501156568527222s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.553794860839844e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2719292640686035s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020082712173461914s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.559647560119629s
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.0005729198455810547s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.251300573348999s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020029544830322266s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.124641418457031e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.512363433837891s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.26587796211242676s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020020246505737305s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.0531158447265625e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.605633974075317s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.00037097930908203125s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.26370787620544434s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02007913589477539s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 5.9604644775390625e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.281200647354126s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.8176364898681641s
Availability | VoID file availability check for AragoDBPedia took 0.0006098747253417969s
Extra | Recovery of all triples for AragoDBPedia took 3.232903003692627s
Performance | Total latancy measurement for AragoDBPedia took 1.9343314170837402s
Amount of data | Number of triples check for AragoDBPedia took 1.2547378540039062s
Interoperability | New terms check for AragoDBPedia took 2.250662088394165s
Versatility | Languages check for AragoDBPedia took 60.520275592803955s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.719388484954834s
Security | Check HTTPS for AragoDBPedia took 0.24616742134094238s
Interpretability | RDF structures check for AragoDBPedia took 0.8479471206665039s
Versatility | Serialization formats check for AragoDBPedia took 0.9922521114349365s
Availability | RDF dump link check for AragoDBPedia took 0.4078843593597412s
License | MR license check for AragoDBPedia took 0.6519515514373779s
License | HR license check for AragoDBPedia took 6.273644924163818s
Amount of data | Number of property check for AragoDBPedia took 0.44892120361328125s
Understandability | Number of label check for AragoDBPedia took 0.5682828426361084s
Understandability | URI regex check for AragoDBPedia took 0.9359538555145264s
Understandability | Vocabs check for AragoDBPedia took 0.4667489528656006s
Verifiability | Authors check for AragoDBPedia took 0.4971578121185303s
Verifiability | Publishers check for AragoDBPedia took 0.5150454044342041s
Performance | Throughput check for AragoDBPedia took 11.978188037872314s
Amount of data | Check the number of entities for AragoDBPedia took 7.700920104980469e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.4632375240325928s
Interlinking | sameAs chians check for AragoDBPedia took 0.43210601806640625s
Interlinking | skos check for AragoDBPedia took 0.6150379180908203s
Interlinking | skos check for AragoDBPedia took 0.43669843673706055s
Timeliness | dataset update frequency check for AragoDBPedia took 1.420194387435913s
Currency | Creation date check for AragoDBPedia took 1.9096896648406982s
Currency | Modification date check for AragoDBPedia took 0.8859972953796387s
Rep.Conc. | URIs length for AragoDBPedia took 5.983146905899048s
Interoperability | New vocabularies check for AragoDBPedia took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.39334726333618164s
Accuracy | Check Functional Property for AragoDBPedia took 0.43840479850769043s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.4425520896911621s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.345832109451294s
Accuracy | Check White space in annotation for AragoDBPedia took 0.027111530303955078s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.027666568756103516s
Consistency | Disjoint class check for AragoDBPedia took 0.4962654113769531s
Consistency | Check Misplaced properties for AragoDBPedia took 4.58818244934082s
Consistency | Misplaced classes for AragoDBPedia took 0.7099511623382568s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.8029592037200928s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3582332134246826s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.6466076374053955s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03441977500915527s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.6191437244415283s
Security | Sign check for AragoDBPedia took 0.556194543838501s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3329.7882170677185s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.8961694240570068s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBPedia took 4.76837158203125e-06s
INFO | --- Analysis for aragodbpedia took 16534.008895158768s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.288501977920532s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.7246909141540527s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.340576171875e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for archiveshub-linkeddata took 84.22072958946228s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.0531158447265625e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.6951868534088135s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020190954208374023s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.266334533691406e-05s
Believability | Calculation of trust value for Archivi ISMA took 5.9604644775390625e-06s
INFO | --- Analysis for archivio-isma took 3.778502941131592s
Availability | SPARQL endpoint availability check for ARIADNE took 3.9577484130859375e-05s
Availability | VoID file availability check for ARIADNE took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2626051902770996s
Reputation | Calculation of the PageRank for ARIADNE took 0.020328521728515625s
Interlinking | Calculation of Degree of Connection for ARIADNE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ARIADNE took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 2.956390380859375e-05s
Believability | Calculation of trust value for ARIADNE took 1.1682510375976562e-05s
INFO | --- Analysis for ariadne took 3.339599132537842s
Availability | SPARQL endpoint availability check for Aristotle University took 4.00543212890625e-05s
Availability | VoID file availability check for Aristotle University took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.278278112411499s
Reputation | Calculation of the PageRank for Aristotle University took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for Aristotle University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 2.8371810913085938e-05s
Believability | Calculation of trust value for Aristotle University took 7.152557373046875e-06s
INFO | --- Analysis for aristotle-university took 2.9905824661254883s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.039551019668579s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.26639795303344727s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 2.9325485229492188e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.3909759521484375e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 21.74644660949707s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.1961669921875e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.26215052604675293s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.0517578125e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 7.62939453125e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.8672597408294678s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.9194424152374268s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.259080171585083s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.021604299545288086s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.076957702636719e-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.409465074539185s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.458427429199219e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.29718661308288574s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00011181831359863281s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.059906005859375e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 8.558124303817749s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 4.3392181396484375e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.2680959701538086s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020787477493286133s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.2159347534179688e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 7.867813110351562e-06s
INFO | --- Analysis for Arthron took 2.3981943130493164s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.38690185546875e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2604408264160156s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010538101196289062s
Believability | Calculation of trust value for Arthroscopy community took 9.5367431640625e-06s
INFO | --- Analysis for arthroscopy took 12.8512282371521s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.9569735527038574s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0006327629089355469s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 0.09673643112182617s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 0.08043694496154785s
Versatility | Languages check for Wikidata entry for Art × Science International took 0.09402012825012207s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.0828864574432373s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.08333826065063477s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.09286761283874512s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.08309388160705566s
License | MR license check for Wikidata entry for Art × Science International took 0.0832357406616211s
License | HR license check for Wikidata entry for Art × Science International took 0.08683252334594727s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.09722375869750977s
Understandability | Number of label check for Wikidata entry for Art × Science International took 0.08430957794189453s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.16570591926574707s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.08898377418518066s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.07132935523986816s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.08563518524169922s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.00015020370483398438s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.08288002014160156s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.08370447158813477s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.07374095916748047s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.0842287540435791s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.08477449417114258s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.15545058250427246s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.16721296310424805s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 0.1574103832244873s
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.08300447463989258s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.07409882545471191s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.09303522109985352s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.4915473461151123s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 0.0001666545867919922s
Security | Sign check for Wikidata entry for Art × Science International took 0.09334254264831543s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.2658853530883789s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.1920928955078125e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 7.152557373046875e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 20.89784288406372s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.519256830215454s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2722597122192383s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.796287536621094e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 12.845916986465454s
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.379911184310913s
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.0006031990051269531s
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.27548646926879883s
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.020599842071533203s
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.0967254638671875e-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.0007236003875732422s
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.177757263183594e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 11.225492715835571s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.374155044555664s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2576167583465576s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.821487426757812e-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 12.149001121520996s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.378631353378296s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2895944118499756s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.1961669921875e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-CRB took 14.348687887191772s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.411545991897583s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.27620410919189453s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.869171142578125e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.647130727767944s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.4147677421569824s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2831258773803711s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.840884923934937s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.397264003753662s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.26250195503234863s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.463859558105469e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 5.4836273193359375e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.720585584640503s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.182783842086792s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.27269530296325684s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.963180541992188e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 13.541296243667603s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.3804104328155518s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2608151435852051s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.316734313964844e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.660839796066284s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.3767335414886475s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.26967477798461914s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007293224334716797s
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 5.9604644775390625e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.56181025505066s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.9413864612579346s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.29799413681030273s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.744529724121094e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 16.066138982772827s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.3940303325653076s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.26474881172180176s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020426034927368164s
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.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.653236389160156e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.082773685455322s
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.3882253170013428s
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.0006549358367919922s
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.26227903366088867s
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.020529747009277344s
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.049041748046875e-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.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.915496826171875e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.680117130279541s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.388089895248413s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2599599361419678s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.553794860839844e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC_-_DNB took 11.10359239578247s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.267692565917969e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.27139902114868164s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020425081253051758s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.437301635742188e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 7.152557373046875e-06s
INFO | --- Analysis for asit took 7.6933839321136475s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 5.412101745605469e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2555887699127197s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.019977331161499023s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.719329833984375e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.1920928955078125e-05s
INFO | --- Analysis for asjp took 5.210896730422974s
Availability | SPARQL endpoint availability check for ASN:US took 0.08675432205200195s
Availability | VoID file availability check for ASN:US took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2693166732788086s
Reputation | Calculation of the PageRank for ASN:US took 0.020154714584350586s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.532669067382812e-05s
Believability | Calculation of trust value for ASN:US took 5.0067901611328125e-06s
INFO | --- Analysis for asn-us took 6.014174461364746s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.220008850097656e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2935466766357422s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007319450378417969s
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 4.5299530029296875e-06s
INFO | --- Analysis for aspire-mmu took 4.511829853057861s
Availability | SPARQL endpoint availability check for associations took 4.291534423828125e-05s
Availability | VoID file availability check for associations took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for associations took 0.25810813903808594s
Reputation | Calculation of the PageRank for associations took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for associations took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for associations took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for associations took 6.604194641113281e-05s
Believability | Calculation of trust value for associations took 6.67572021484375e-06s
INFO | --- Analysis for associations took 7.149548768997192s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.291534423828125e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.269728422164917s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.0040740966796875e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 6.4373016357421875e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 3.0220088958740234s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.315376281738281e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.25810718536376953s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.606910705566406e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 7.867813110351562e-06s
INFO | --- Analysis for athelia-rfid took 4.085291147232056s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.220008850097656e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.260800838470459s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.361701965332031e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.9651806354522705s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.48104214668273926s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.25791454315185547s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.125999450683594e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 8.344650268554688e-06s
INFO | --- Analysis for AugustiniConfessiones took 3.9028780460357666s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.530963659286499s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.28522777557373047s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.083747863769531e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 9.5367431640625e-06s
INFO | --- Analysis for austrian_ski_racers took 3.7661211490631104s
Availability | SPARQL endpoint availability check for AVsOnto took 4.3392181396484375e-05s
Availability | VoID file availability check for AVsOnto took 0.00034356117248535156s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.255601167678833s
Reputation | Calculation of the PageRank for AVsOnto took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.218650817871094e-05s
Believability | Calculation of trust value for AVsOnto took 7.62939453125e-06s
INFO | --- Analysis for AVsOnto took 3.358024835586548s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21074485778808594s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005602836608886719s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 178.9837682247162s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5131618976593018s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0973746776581s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 196.5393204689026s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1037402153015s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.02427339553833s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2726600170135498s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1341562271118164s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23193669319152832s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09687423706054688s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 51.29263687133789s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1034936904907s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20116186141967773s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1014931201935s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21762585639953613s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11848115921020508s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.08985018730163574s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09824252128601074s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.434926271438599s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.343292236328125e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.08637762069702148s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0888366699219s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1305551528930664s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09875726699829102s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12533283233642578s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2980062961578369s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22327661514282227s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 499.52910804748535s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20679616928100586s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 31.35896897315979s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.256584644317627s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.784290313720703s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20742154121398926s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1240725517273s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 315.86123299598694s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.3800995349884033s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.5635783672333s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.79390287399292s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10661029815673828s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.730525255203247s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6902079582214355s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021091938018798828s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.985664367675781e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9073486328125e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.4836273193359375e-06s
INFO | --- Analysis for b3kat took 4333.978739023209s
Availability | SPARQL endpoint availability check for BabelNet took 0.6073014736175537s
Availability | VoID file availability check for BabelNet took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for BabelNet took 0.753899097442627s
Reputation | Calculation of the PageRank for BabelNet took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001614093780517578s
Believability | Calculation of trust value for BabelNet took 7.152557373046875e-06s
INFO | --- Analysis for babelnet took 7.01590371131897s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.363059997558594e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.24966812133789062s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bacevicius.lt took 7.62939453125e-06s
INFO | --- Analysis for Bacevicius.lt took 3.3128368854522705s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.49535036087036133s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2524383068084717s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020137310028076172s
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.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.0531158447265625e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 7.3909759521484375e-06s
INFO | --- Analysis for bag took 4.566174268722534s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.6124229431152344s
Availability | VoID file availability check for 红色经典歌曲 took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.24683213233947754s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9325485229492188e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.67572021484375e-06s
INFO | --- Analysis for baixue took 2.9182839393615723s
Availability | SPARQL endpoint availability check for baixue composer took 5.745887756347656e-05s
Availability | VoID file availability check for baixue composer took 0.000331878662109375s
Completeness | Calculation of interlinking completeness for baixue composer took 0.2504422664642334s
Reputation | Calculation of the PageRank for baixue composer took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for baixue composer took 2.8133392333984375e-05s
Believability | Calculation of trust value for baixue composer took 8.106231689453125e-06s
INFO | --- Analysis for baixue_composer took 2.9721763134002686s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.458427429199219e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2669684886932373s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9087066650390625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.67572021484375e-06s
INFO | --- Analysis for baixue_imagery took 2.7105274200439453s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.1961669921875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.00037169456481933594s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.24634027481079102s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020217418670654297s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.7894973754882812e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue_imagery1 took 3.2730343341827393s
Availability | SPARQL endpoint availability check for BAMS took 4.1961669921875e-05s
Availability | VoID file availability check for BAMS took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for BAMS took 0.25134754180908203s
Reputation | Calculation of the PageRank for BAMS took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for BAMS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BAMS took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for BAMS took 2.9325485229492188e-05s
Believability | Calculation of trust value for BAMS took 7.152557373046875e-06s
INFO | --- Analysis for bams took 2.803126335144043s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.1961669921875e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.00037026405334472656s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2575647830963135s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020287036895751953s
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.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.743171691894531e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 7.62939453125e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.0130772590637207s
Availability | SPARQL endpoint availability check for BBC Music took 0.3343327045440674s
Availability | VoID file availability check for BBC Music took 0.0003921985626220703s
Completeness | Calculation of interlinking completeness for BBC Music took 0.2774925231933594s
Reputation | Calculation of the PageRank for BBC Music took 0.020949363708496094s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012826919555664062s
Believability | Calculation of trust value for BBC Music took 1.3828277587890625e-05s
INFO | --- Analysis for bbc-music took 3.2939202785491943s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.2207777500152588s
Availability | VoID file availability check for BBC Programmes took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2519381046295166s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.0001010894775390625s
Believability | Calculation of trust value for BBC Programmes took 6.9141387939453125e-06s
INFO | --- Analysis for bbc-programmes took 11.135242938995361s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.2029130458831787s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0008692741394042969s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.26463842391967773s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020945072174072266s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0009992122650146484s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.0001201629638671875s
Believability | Calculation of trust value for BBC Wildlife Finder took 7.62939453125e-06s
INFO | --- Analysis for bbc-wildlife-finder took 10.827787399291992s
Availability | SPARQL endpoint availability check for BBOP took 5.9604644775390625e-05s
Availability | VoID file availability check for BBOP took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for BBOP took 0.27039003372192383s
Reputation | Calculation of the PageRank for BBOP took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for BBOP took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.337860107421875e-05s
Believability | Calculation of trust value for BBOP took 8.344650268554688e-06s
INFO | --- Analysis for bbop took 2.942991018295288s
Availability | SPARQL endpoint availability check for BBOP took 4.458427429199219e-05s
Availability | VoID file availability check for BBOP took 0.0010199546813964844s
Completeness | Calculation of interlinking completeness for BBOP took 0.25989317893981934s
Reputation | Calculation of the PageRank for BBOP took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for BBOP took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.0279159545898438e-05s
Believability | Calculation of trust value for BBOP took 7.867813110351562e-06s
INFO | --- Analysis for bbop-selected took 19.938125371932983s
Availability | SPARQL endpoint availability check for Bdgp took 1.6120193004608154s
Availability | VoID file availability check for Bdgp took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2716047763824463s
Reputation | Calculation of the PageRank for Bdgp took 0.02021002769470215s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.123283386230469e-05s
Believability | Calculation of trust value for Bdgp took 7.867813110351562e-06s
INFO | --- Analysis for bdgp took 8.404210329055786s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.315376281738281e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.257580041885376s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bendev Junior took 6.9141387939453125e-06s
INFO | --- Analysis for bendevoficial took 5.264696359634399s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 5.229438066482544s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.26191091537475586s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.914138793945312e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.4836273193359375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 13.059758424758911s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.0531158447265625e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.2861332893371582s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.021108627319335938s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 4.100799560546875e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 9.298324584960938e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.940220594406128s
Availability | SPARQL endpoint availability check for berlios took 4.38690185546875e-05s
Availability | VoID file availability check for berlios took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for berlios took 0.2534821033477783s
Reputation | Calculation of the PageRank for berlios took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for berlios took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for berlios took 8.7738037109375e-05s
Believability | Calculation of trust value for berlios took 7.3909759521484375e-06s
INFO | --- Analysis for berlios took 2.839876890182495s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.1961669921875e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3443307876586914s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.771087646484375e-05s
Believability | Calculation of trust value for Between Our Worlds took 8.344650268554688e-06s
INFO | --- Analysis for betweenourworlds took 9.459190607070923s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.5931510925292969s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.2834165096282959s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.012222290039062e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for bfs-linked-data took 3.2518582344055176s
Availability | SPARQL endpoint availability check for BibBase took 0.07476162910461426s
Availability | VoID file availability check for BibBase took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for BibBase took 0.29595518112182617s
Reputation | Calculation of the PageRank for BibBase took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BibBase took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.298324584960938e-05s
Believability | Calculation of trust value for BibBase took 1.0728836059570312e-05s
INFO | --- Analysis for bibbase took 2.4818572998046875s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.553794860839844e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2838878631591797s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00010442733764648438s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 5.6008899211883545s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.5299530029296875e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.27866339683532715s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.000110626220703125s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 8.344650268554688e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 8.179883241653442s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.28968095779418945s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.049041748046875e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.990468740463257s
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.00040411949157714844s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2888212203979492s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.600120544433594e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 8.344650268554688e-06s
INFO | --- Analysis for BibSonomy took 9.611087322235107s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.220008850097656e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2642238140106201s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020666122436523438s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.147125244140625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 7.152557373046875e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 4.815629959106445s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 7.152557373046875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.28109288215637207s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.0040740966796875e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 8.58306884765625e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.5448620319366455s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 5.030632019042969e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2526054382324219s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.02047562599182129s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.8758885860443115s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.9088056087493896s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006551742553710938s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 39.60112500190735s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5123875141143799s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.304258823394775s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.21537184715271s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.11338973045349s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1416785717010498s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.987933874130249s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.2652261257171631s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 6.2240259647369385s
License | MR license check for Bio2RDF::Affymetrix took 0.37479066848754883s
License | HR license check for Bio2RDF::Affymetrix took 60.08857846260071s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.1421983242034912s
Understandability | Number of label check for Bio2RDF::Affymetrix took 11.090731143951416s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.42870616912841797s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.14296174049377441s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.1997816562652588s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.1339552402496338s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.674733400344849s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 73.61409020423889s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.5927786827087402s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.20662450790405273s
Interlinking | skos check for Bio2RDF::Affymetrix took 1.3350439071655273s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.19773292541503906s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.13870692253112793s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2772552967071533s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.26000213623046875s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 119.75954222679138s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.3406553268432617s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15790963172912598s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.14838051795959473s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 18.614829540252686s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8969552516937256s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6652874946594238s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.3258378505706787s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 70.46376085281372s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.317002058029175s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 12.844765663146973s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.341745138168335s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.438732385635376s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.6995773315429688s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3564720153808594s
Security | Sign check for Bio2RDF::Affymetrix took 0.12642240524291992s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 12.0704505443573s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.8027503490447998s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.799003601074219e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1065.0158669948578s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.4915590286254883s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0005581378936767578s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 35.69045662879944s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2605934143066406s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 44.30461144447327s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.960278272628784s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25747275352478s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2617650032043457s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.1569521427154541s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 1.1813545227050781s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3664560317993164s
Availability | RDF dump link check for Bio2RDF::Biomodels took 6.452638626098633s
License | MR license check for Bio2RDF::Biomodels took 0.5038695335388184s
License | HR license check for Bio2RDF::Biomodels took 60.266895055770874s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.28515052795410156s
Understandability | Number of label check for Bio2RDF::Biomodels took 11.814200162887573s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5973734855651855s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.285891056060791s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.27092623710632324s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.25696778297424316s
Performance | Throughput check for Bio2RDF::Biomodels took 11.278416156768799s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 76.86553978919983s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.581233024597168s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3442404270172119s
Interlinking | skos check for Bio2RDF::Biomodels took 0.8290326595306396s
Interlinking | skos check for Bio2RDF::Biomodels took 0.44170093536376953s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2872767448425293s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5254037380218506s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5225670337677002s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 120.69515323638916s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.4078090190887451s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.28290605545043945s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.29981279373168945s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 17.921140670776367s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9038166999816895s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6605327129364014s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4964759349822998s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 72.16503047943115s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4541196823120117s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 11.300192832946777s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3393158912658691s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.58248972892761s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7022190093994141s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.45586323738098145s
Security | Sign check for Bio2RDF::Biomodels took 0.28899264335632324s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 12.331151485443115s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 1.4512908458709717s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012421607971191406s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1074.854630947113s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0007960796356201172s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.7343032360076904s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 5.260287761688232s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.4638862609863281s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006437301635742188s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 36.08646488189697s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2890660762786865s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 44.33182215690613s
Interoperability | New terms check for Bio2RDF::Bioportal took 44.45104908943176s
Versatility | Languages check for Bio2RDF::Bioportal took 60.26209378242493s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.27489805221557617s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.1668243408203125s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 1.0064609050750732s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3519604206085205s
Availability | RDF dump link check for Bio2RDF::Bioportal took 6.373799562454224s
License | MR license check for Bio2RDF::Bioportal took 0.5753061771392822s
License | HR license check for Bio2RDF::Bioportal took 60.23001432418823s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.256389856338501s
Understandability | Number of label check for Bio2RDF::Bioportal took 11.590624809265137s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6092662811279297s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2808194160461426s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2628154754638672s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.267437219619751s
Performance | Throughput check for Bio2RDF::Bioportal took 11.416746854782104s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 76.01522088050842s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.27890801429748535s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3919260501861572s
Interlinking | skos check for Bio2RDF::Bioportal took 0.7280969619750977s
Interlinking | skos check for Bio2RDF::Bioportal took 0.34314489364624023s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.25051307678222656s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5290708541870117s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5352084636688232s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 121.6739706993103s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.41654229164123535s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.28353333473205566s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2882852554321289s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 18.564122676849365s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8889486789703369s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6502523422241211s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4337177276611328s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 70.73427987098694s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4061343669891357s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 11.810487031936646s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3112196922302246s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.59197759628296s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.6955318450927734s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.4527270793914795s
Security | Sign check for Bio2RDF::Bioportal took 0.28165721893310547s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 12.124161005020142s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.42708444595336914s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020833730697631836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00042939186096191406s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1079.2877807617188s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.13596582412719727s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0007927417755126953s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.26432275772094727s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020076274871826172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.340576171875e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-chembl took 18.067031860351562s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.47188568115234375s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006208419799804688s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 35.17462706565857s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2523679733276367s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 43.76532578468323s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 43.187204122543335s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.245760679244995s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.29010653495788574s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.14496254920959473s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.8667333126068115s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.34552526473999023s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 6.375554800033569s
License | MR license check for Bio2RDF::Clinicaltrials took 0.477283239364624s
License | HR license check for Bio2RDF::Clinicaltrials took 60.23852729797363s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.27440905570983887s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.361166000366211s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5950272083282471s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2610352039337158s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.28577589988708496s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.28344011306762695s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 10.424504518508911s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 76.78619241714478s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.5884594917297363s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3639192581176758s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7787497043609619s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.40199851989746094s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2861764430999756s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5153355598449707s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5586674213409424s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 121.81786036491394s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4016432762145996s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.28798675537109375s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2693626880645752s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 17.78128719329834s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8945820331573486s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6579153537750244s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.47989869117736816s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 70.61909484863281s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.384042739868164s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 12.540338516235352s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3223457336425781s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.58328366279602s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.6984150409698486s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.43180084228515625s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2839531898498535s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 11.915001392364502s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 1.0859401226043701s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.936622619628906e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1066.9959886074066s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.5013124942779541s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005812644958496094s
Extra | Recovery of all triples for Bio2RDF::Ctd took 35.9570894241333s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2867732048034668s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.17514371871948s
Interoperability | New terms check for Bio2RDF::Ctd took 42.50365209579468s
Versatility | Languages check for Bio2RDF::Ctd took 60.245580434799194s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.28339219093322754s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1445004940032959s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.9468812942504883s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3719451427459717s
Availability | RDF dump link check for Bio2RDF::Ctd took 6.199740886688232s
License | MR license check for Bio2RDF::Ctd took 0.5231292247772217s
License | HR license check for Bio2RDF::Ctd took 60.25270652770996s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.27371835708618164s
Understandability | Number of label check for Bio2RDF::Ctd took 11.438122272491455s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6282265186309814s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2749059200286865s
Verifiability | Authors check for Bio2RDF::Ctd took 0.28359198570251465s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.26140761375427246s
Performance | Throughput check for Bio2RDF::Ctd took 11.006076335906982s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 77.53656506538391s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.29444360733032227s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.34395813941955566s
Interlinking | skos check for Bio2RDF::Ctd took 0.7385220527648926s
Interlinking | skos check for Bio2RDF::Ctd took 0.35806918144226074s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2988166809082031s
Currency | Creation date check for Bio2RDF::Ctd took 0.5525929927825928s
Currency | Modification date check for Bio2RDF::Ctd took 0.5325450897216797s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 119.80411124229431s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4483358860015869s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2613790035247803s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2846033573150635s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 19.436020135879517s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8953390121459961s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6671969890594482s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.39289212226867676s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 70.35468244552612s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.5709848403930664s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 12.067161560058594s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3426792621612549s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.607946157455444s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7163684368133545s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4474799633026123s
Security | Sign check for Bio2RDF::Ctd took 0.28159427642822266s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 12.476232290267944s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.8046739101409912s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.961822509765625e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ctd took 1079.4851734638214s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.291534423828125e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.6986055374145508s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.125999450683594e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-dataset took 4.915966987609863s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.47136425971984863s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005743503570556641s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 33.549434185028076s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2575578689575195s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.74951195716858s
Interoperability | New terms check for Bio2RDF::Dbsnp took 45.25056338310242s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.2541184425354s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.26569509506225586s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1570875644683838s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.9909152984619141s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.3531486988067627s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 6.299688100814819s
License | MR license check for Bio2RDF::Dbsnp took 0.5556707382202148s
License | HR license check for Bio2RDF::Dbsnp took 60.261232137680054s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2806742191314697s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.015733480453491s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5841696262359619s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.25539588928222656s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.27815818786621094s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.26194190979003906s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.839525699615479s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 79.85472989082336s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.5918533802032471s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.35614943504333496s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8632352352142334s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3739595413208008s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2620851993560791s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5443854331970215s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5209991931915283s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 123.70353674888611s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4631500244140625s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.27245593070983887s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2731902599334717s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 18.76882290840149s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8962881565093994s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6687703132629395s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.4758012294769287s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 70.62855267524719s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.425001859664917s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 11.957138061523438s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.343919038772583s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.585463523864746s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.6968083381652832s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.42949819564819336s
Security | Sign check for Bio2RDF::Dbsnp took 0.2847294807434082s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 12.567059516906738s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 1.442018985748291s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.389617919921875e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1076.4859991073608s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4809763431549072s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005719661712646484s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 36.02771973609924s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.3066773414611816s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 46.53895378112793s
Interoperability | New terms check for Bio2RDF::Drugbank took 42.89457130432129s
Versatility | Languages check for Bio2RDF::Drugbank took 60.25397753715515s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.26914334297180176s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.17284274101257324s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.7782275676727295s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3185582160949707s
Availability | RDF dump link check for Bio2RDF::Drugbank took 6.302323818206787s
License | MR license check for Bio2RDF::Drugbank took 0.4811701774597168s
License | HR license check for Bio2RDF::Drugbank took 60.22965478897095s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2536942958831787s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.747421503067017s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.6234562397003174s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.27161359786987305s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2738001346588135s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.24965381622314453s
Performance | Throughput check for Bio2RDF::Drugbank took 10.950781106948853s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 74.12795281410217s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.4168250560760498s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.3615117073059082s
Interlinking | skos check for Bio2RDF::Drugbank took 0.7707324028015137s
Interlinking | skos check for Bio2RDF::Drugbank took 0.36054253578186035s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2811930179595947s
Currency | Creation date check for Bio2RDF::Drugbank took 0.551579475402832s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5278840065002441s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 124.68370294570923s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4548959732055664s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2876167297363281s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.26856136322021484s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 19.57331609725952s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.9066500663757324s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6589362621307373s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.43070030212402344s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 70.57174181938171s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.5234360694885254s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 11.539274454116821s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.2864067554473877s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.54810166358948s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6878626346588135s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.40749144554138184s
Security | Sign check for Bio2RDF::Drugbank took 0.28163576126098633s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 12.653652667999268s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.9795825481414795s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011539459228515625s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1085.7306134700775s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.47128820419311523s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006401538848876953s
Extra | Recovery of all triples for Bio2RDF::Genage took 35.016767501831055s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2865376472473145s
Amount of data | Number of triples check for Bio2RDF::Genage took 44.1483359336853s
Interoperability | New terms check for Bio2RDF::Genage took 46.12535262107849s
Versatility | Languages check for Bio2RDF::Genage took 60.246209383010864s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2900655269622803s
Security | Check HTTPS for Bio2RDF::Genage took 0.15833115577697754s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.8033552169799805s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3543055057525635s
Availability | RDF dump link check for Bio2RDF::Genage took 6.267755508422852s
License | MR license check for Bio2RDF::Genage took 0.4705369472503662s
License | HR license check for Bio2RDF::Genage took 60.232266902923584s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2530040740966797s
Understandability | Number of label check for Bio2RDF::Genage took 10.786672592163086s
Understandability | URI regex check for Bio2RDF::Genage took 0.5990958213806152s
Understandability | Vocabs check for Bio2RDF::Genage took 0.26429247856140137s
Verifiability | Authors check for Bio2RDF::Genage took 0.28230881690979004s
Verifiability | Publishers check for Bio2RDF::Genage took 0.27895116806030273s
Performance | Throughput check for Bio2RDF::Genage took 10.597772359848022s
Amount of data | Check the number of entities for Bio2RDF::Genage took 73.0564477443695s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.6015224456787109s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.36535048484802246s
Interlinking | skos check for Bio2RDF::Genage took 0.8918700218200684s
Interlinking | skos check for Bio2RDF::Genage took 0.35863161087036133s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2801992893218994s
Currency | Creation date check for Bio2RDF::Genage took 0.5123353004455566s
Currency | Modification date check for Bio2RDF::Genage took 0.5393741130828857s
Rep.Conc. | URIs length for Bio2RDF::Genage took 121.0169005393982s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.45187973976135254s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2724423408508301s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.266345739364624s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 18.85376238822937s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.9075503349304199s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6625475883483887s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4503912925720215s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 71.34611654281616s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.43392014503479s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 12.250787496566772s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3284051418304443s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.58074331283569s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7313253879547119s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.44725966453552246s
Security | Sign check for Bio2RDF::Genage took 0.2803175449371338s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 12.518156051635742s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 1.0279860496520996s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.9604644775390625e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-genage took 1069.9852800369263s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.2682182788848877s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.175041198730469e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-genbank took 5.194091081619263s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 1.2866885662078857s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006556510925292969s
Extra | Recovery of all triples for Bio2RDF::Gendr took 37.33299279212952s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2461748123168945s
Amount of data | Number of triples check for Bio2RDF::Gendr took 44.08985233306885s
Interoperability | New terms check for Bio2RDF::Gendr took 43.056973695755005s
Versatility | Languages check for Bio2RDF::Gendr took 60.25155735015869s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2595031261444092s
Security | Check HTTPS for Bio2RDF::Gendr took 0.14748477935791016s
Interpretability | RDF structures check for Bio2RDF::Gendr took 1.1338651180267334s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.34576869010925293s
Availability | RDF dump link check for Bio2RDF::Gendr took 6.382004261016846s
License | MR license check for Bio2RDF::Gendr took 0.43874144554138184s
License | HR license check for Bio2RDF::Gendr took 60.23143482208252s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2734653949737549s
Understandability | Number of label check for Bio2RDF::Gendr took 10.77986741065979s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5838723182678223s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2500572204589844s
Verifiability | Authors check for Bio2RDF::Gendr took 0.27423930168151855s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2799041271209717s
Performance | Throughput check for Bio2RDF::Gendr took 11.205362796783447s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 75.29463076591492s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.7351539134979248s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3903348445892334s
Interlinking | skos check for Bio2RDF::Gendr took 1.162154197692871s
Interlinking | skos check for Bio2RDF::Gendr took 0.3442702293395996s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2627601623535156s
Currency | Creation date check for Bio2RDF::Gendr took 0.5333514213562012s
Currency | Modification date check for Bio2RDF::Gendr took 0.5253336429595947s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 122.99542379379272s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.42653632164001465s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2833678722381592s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2981259822845459s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 18.109649181365967s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8958418369293213s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6808459758758545s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.49734044075012207s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 70.03640818595886s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4384498596191406s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 11.28264331817627s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3190371990203857s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.53959274291992s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.6925585269927979s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.4691145420074463s
Security | Sign check for Bio2RDF::Gendr took 0.2743527889251709s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 13.003230333328247s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.7938272953033447s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.793571472167969e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-gendr took 1072.6749176979065s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4519014358520508s
Availability | VoID file availability check for Bio2RDF::Goa took 0.00032711029052734375s
Extra | Recovery of all triples for Bio2RDF::Goa took 35.85210657119751s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2681102752685547s
Amount of data | Number of triples check for Bio2RDF::Goa took 43.958577394485474s
Interoperability | New terms check for Bio2RDF::Goa took 42.919184923172s
Versatility | Languages check for Bio2RDF::Goa took 60.252296686172485s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.27105236053466797s
Security | Check HTTPS for Bio2RDF::Goa took 0.14764857292175293s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.27779531478881836s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.32852983474731445s
Availability | RDF dump link check for Bio2RDF::Goa took 6.2725746631622314s
License | MR license check for Bio2RDF::Goa took 0.4822084903717041s
License | HR license check for Bio2RDF::Goa took 60.24149179458618s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2760918140411377s
Understandability | Number of label check for Bio2RDF::Goa took 10.514948606491089s
Understandability | URI regex check for Bio2RDF::Goa took 0.5882048606872559s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2668938636779785s
Verifiability | Authors check for Bio2RDF::Goa took 0.2606644630432129s
Verifiability | Publishers check for Bio2RDF::Goa took 0.25484776496887207s
Performance | Throughput check for Bio2RDF::Goa took 10.867599964141846s
Amount of data | Check the number of entities for Bio2RDF::Goa took 79.91156029701233s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.27556753158569336s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.37813282012939453s
Interlinking | skos check for Bio2RDF::Goa took 0.8864345550537109s
Interlinking | skos check for Bio2RDF::Goa took 0.36011433601379395s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.3119931221008301s
Currency | Creation date check for Bio2RDF::Goa took 0.5247008800506592s
Currency | Modification date check for Bio2RDF::Goa took 0.5239317417144775s
Rep.Conc. | URIs length for Bio2RDF::Goa took 120.32791137695312s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.44643211364746094s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.29147815704345703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.28252649307250977s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 19.22858428955078s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.9026434421539307s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6769781112670898s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4087512493133545s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 71.56929421424866s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.566849708557129s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 11.386016845703125s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3035571575164795s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.52959609031677s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.6988136768341064s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.459484338760376s
Security | Sign check for Bio2RDF::Goa took 0.26606249809265137s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 11.96014142036438s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.9622945785522461s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 7.033348083496094e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-goa took 1080.0891270637512s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.46628570556640625s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006058216094970703s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 36.89168071746826s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2564003467559814s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 44.449424266815186s
Interoperability | New terms check for Bio2RDF::Hgnc took 43.84534168243408s
Versatility | Languages check for Bio2RDF::Hgnc took 60.25592374801636s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2696268558502197s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.1434338092803955s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.9140331745147705s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3632471561431885s
Availability | RDF dump link check for Bio2RDF::Hgnc took 6.358990907669067s
License | MR license check for Bio2RDF::Hgnc took 0.4490480422973633s
License | HR license check for Bio2RDF::Hgnc took 60.24586892127991s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2861783504486084s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.222853899002075s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5734891891479492s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.2770075798034668s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.30196499824523926s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.634911298751831s
Performance | Throughput check for Bio2RDF::Hgnc took 10.999044179916382s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 78.14251947402954s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.5841412544250488s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.36434483528137207s
Interlinking | skos check for Bio2RDF::Hgnc took 0.782052755355835s
Interlinking | skos check for Bio2RDF::Hgnc took 0.352888822555542s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.29676103591918945s
Currency | Creation date check for Bio2RDF::Hgnc took 0.534121036529541s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5607426166534424s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 120.74387383460999s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4408712387084961s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2631089687347412s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2876448631286621s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 18.262144088745117s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8895392417907715s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.666736364364624s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.42414093017578125s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 71.4096565246582s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.4892351627349854s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 12.460723161697388s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3049156665802002s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.518080949783325s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.707251787185669s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4546358585357666s
Security | Sign check for Bio2RDF::Hgnc took 0.29694032669067383s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 13.036513805389404s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 1.3535168170928955s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010776519775390625s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1080.0464432239532s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.4633059501647949s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0005605220794677734s
Extra | Recovery of all triples for Bio2RDF::Homologene took 35.007022857666016s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2585551738739014s
Amount of data | Number of triples check for Bio2RDF::Homologene took 44.29890990257263s
Interoperability | New terms check for Bio2RDF::Homologene took 43.05242323875427s
Versatility | Languages check for Bio2RDF::Homologene took 60.28974199295044s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.27077484130859375s
Security | Check HTTPS for Bio2RDF::Homologene took 0.1546485424041748s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.9850220680236816s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.34348607063293457s
Availability | RDF dump link check for Bio2RDF::Homologene took 6.346007347106934s
License | MR license check for Bio2RDF::Homologene took 0.5141255855560303s
License | HR license check for Bio2RDF::Homologene took 60.25714445114136s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.29848384857177734s
Understandability | Number of label check for Bio2RDF::Homologene took 10.195698976516724s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6091964244842529s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.267139196395874s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2768425941467285s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2489461898803711s
Performance | Throughput check for Bio2RDF::Homologene took 11.205257415771484s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 73.90709400177002s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.5996150970458984s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.34879064559936523s
Interlinking | skos check for Bio2RDF::Homologene took 0.9058973789215088s
Interlinking | skos check for Bio2RDF::Homologene took 0.3367273807525635s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.287036657333374s
Currency | Creation date check for Bio2RDF::Homologene took 0.5513033866882324s
Currency | Modification date check for Bio2RDF::Homologene took 0.544367790222168s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 121.02861785888672s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.42707085609436035s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2792234420776367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.26137709617614746s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 18.882097005844116s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8956305980682373s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6762807369232178s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.38950061798095703s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 70.47686433792114s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4805474281311035s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 11.24181580543518s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3463702201843262s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.57852840423584s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7129945755004883s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4101414680480957s
Security | Sign check for Bio2RDF::Homologene took 0.29878759384155273s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 13.207502841949463s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 1.007544994354248s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.698204040527344e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-homologene took 1071.8352587223053s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.7135961055755615s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-inoh took 5.166911602020264s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.4601421356201172s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.00066375732421875s
Extra | Recovery of all triples for Bio2RDF::Interpro took 35.573975801467896s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.3025212287902832s
Amount of data | Number of triples check for Bio2RDF::Interpro took 46.4786593914032s
Interoperability | New terms check for Bio2RDF::Interpro took 44.00961971282959s
Versatility | Languages check for Bio2RDF::Interpro took 60.25413537025452s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.27796149253845215s
Security | Check HTTPS for Bio2RDF::Interpro took 0.16971349716186523s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.7957675457000732s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3452463150024414s
Availability | RDF dump link check for Bio2RDF::Interpro took 6.1941587924957275s
License | MR license check for Bio2RDF::Interpro took 0.5882565975189209s
License | HR license check for Bio2RDF::Interpro took 60.23134899139404s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2614555358886719s
Understandability | Number of label check for Bio2RDF::Interpro took 10.974371910095215s
Understandability | URI regex check for Bio2RDF::Interpro took 0.6171913146972656s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.26661086082458496s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2842724323272705s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.2827332019805908s
Performance | Throughput check for Bio2RDF::Interpro took 11.062053680419922s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 75.64144921302795s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.5891084671020508s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.41538238525390625s
Interlinking | skos check for Bio2RDF::Interpro took 0.9653828144073486s
Interlinking | skos check for Bio2RDF::Interpro took 0.4189486503601074s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.298551082611084s
Currency | Creation date check for Bio2RDF::Interpro took 0.5273885726928711s
Currency | Modification date check for Bio2RDF::Interpro took 0.5033493041992188s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 123.20555233955383s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4315011501312256s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.29112815856933594s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.27034759521484375s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 17.54734182357788s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.9003081321716309s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6635227203369141s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.43576669692993164s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 71.04528737068176s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.4214677810668945s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 12.853840827941895s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.361201524734497s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.60381054878235s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7017483711242676s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4432260990142822s
Security | Sign check for Bio2RDF::Interpro took 0.27352023124694824s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 12.668669700622559s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.8302061557769775s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 9.846687316894531e-05s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-interpro took 1072.933448791504s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.13368821144104004s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.7506394386291504s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020048856735229492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.510185241699219e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-iproclass took 18.522497177124023s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4808008670806885s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0005688667297363281s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 33.72228026390076s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.280045986175537s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.57520008087158s
Interoperability | New terms check for Bio2RDF::Irefindex took 42.10319781303406s
Versatility | Languages check for Bio2RDF::Irefindex took 60.23626661300659s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2922806739807129s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15625381469726562s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.6735529899597168s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3288872241973877s
Availability | RDF dump link check for Bio2RDF::Irefindex took 6.312971115112305s
License | MR license check for Bio2RDF::Irefindex took 0.5313210487365723s
License | HR license check for Bio2RDF::Irefindex took 60.262624979019165s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.26141858100891113s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.227348327636719s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.6055862903594971s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2571127414703369s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2643723487854004s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2641727924346924s
Performance | Throughput check for Bio2RDF::Irefindex took 10.661665201187134s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 74.58535051345825s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.604846715927124s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3716771602630615s
Interlinking | skos check for Bio2RDF::Irefindex took 0.849766731262207s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3504829406738281s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2897350788116455s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5347425937652588s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5237696170806885s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 123.94782781600952s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.40233373641967773s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.28621983528137207s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.27265214920043945s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 19.039094924926758s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.9081144332885742s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6664872169494629s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.42003941535949707s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 70.03174543380737s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.4317307472229004s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 11.76776933670044s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3164424896240234s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.58603596687317s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7042908668518066s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.44601011276245117s
Security | Sign check for Bio2RDF::Irefindex took 0.2719449996948242s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 12.615131139755249s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 1.3852837085723877s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.225440979003906e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1070.4568665027618s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.7062556743621826s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.02013564109802246s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.580352783203125e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-kegg took 4.236450433731079s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2715933322906494s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.3855438232421875e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.3823471069335938s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13454723358154297s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2985382080078125s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.140686511993408s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.47293710708618164s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005738735198974609s
Extra | Recovery of all triples for Bio2RDF::Lsr took 37.45458769798279s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.265049934387207s
Amount of data | Number of triples check for Bio2RDF::Lsr took 44.170066356658936s
Interoperability | New terms check for Bio2RDF::Lsr took 45.00637722015381s
Versatility | Languages check for Bio2RDF::Lsr took 60.2598774433136s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.27283430099487305s
Security | Check HTTPS for Bio2RDF::Lsr took 0.1571958065032959s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.6614115238189697s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.32720351219177246s
Availability | RDF dump link check for Bio2RDF::Lsr took 6.244038820266724s
License | MR license check for Bio2RDF::Lsr took 0.4416484832763672s
License | HR license check for Bio2RDF::Lsr took 60.25656604766846s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.27960658073425293s
Understandability | Number of label check for Bio2RDF::Lsr took 10.180238723754883s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5939533710479736s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.26395630836486816s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2648587226867676s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.26477479934692383s
Performance | Throughput check for Bio2RDF::Lsr took 11.228731632232666s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 77.12165880203247s
Verifiability | Contribs. check for Bio2RDF::Lsr took 1.0918681621551514s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.34700584411621094s
Interlinking | skos check for Bio2RDF::Lsr took 0.9235010147094727s
Interlinking | skos check for Bio2RDF::Lsr took 0.37529635429382324s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2739288806915283s
Currency | Creation date check for Bio2RDF::Lsr took 0.5530970096588135s
Currency | Modification date check for Bio2RDF::Lsr took 0.5185418128967285s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 119.03750562667847s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4399116039276123s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2789008617401123s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2915186882019043s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 17.195756673812866s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8942184448242188s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6591892242431641s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.43179774284362793s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 72.39206624031067s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.403357982635498s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 11.14706826210022s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3010156154632568s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.61003828048706s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7097733020782471s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4386425018310547s
Security | Sign check for Bio2RDF::Lsr took 0.2822411060333252s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 12.873873233795166s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 1.4982953071594238s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.91278076171875e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-lsr took 1070.8882458209991s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.4737999439239502s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0005950927734375s
Extra | Recovery of all triples for Bio2RDF::Mesh took 36.59279990196228s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2748322486877441s
Amount of data | Number of triples check for Bio2RDF::Mesh took 44.136757135391235s
Interoperability | New terms check for Bio2RDF::Mesh took 42.86993384361267s
Versatility | Languages check for Bio2RDF::Mesh took 60.252821922302246s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.27080488204956055s
Security | Check HTTPS for Bio2RDF::Mesh took 0.14688944816589355s
Interpretability | RDF structures check for Bio2RDF::Mesh took 1.0704410076141357s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.3368337154388428s
Availability | RDF dump link check for Bio2RDF::Mesh took 6.41023325920105s
License | MR license check for Bio2RDF::Mesh took 0.4549243450164795s
License | HR license check for Bio2RDF::Mesh took 60.26149797439575s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2832343578338623s
Understandability | Number of label check for Bio2RDF::Mesh took 10.770989179611206s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5941636562347412s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.25295376777648926s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2774665355682373s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2556319236755371s
Performance | Throughput check for Bio2RDF::Mesh took 10.671585083007812s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 76.11811923980713s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.5816962718963623s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.4202110767364502s
Interlinking | skos check for Bio2RDF::Mesh took 1.0497465133666992s
Interlinking | skos check for Bio2RDF::Mesh took 0.3824176788330078s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.27744460105895996s
Currency | Creation date check for Bio2RDF::Mesh took 0.5451288223266602s
Currency | Modification date check for Bio2RDF::Mesh took 0.5230729579925537s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 120.64035677909851s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.43897438049316406s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2697327136993408s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.292860746383667s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 18.779184103012085s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8928396701812744s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6673691272735596s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4411008358001709s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 70.30056715011597s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.399832010269165s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 11.742313623428345s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.2975349426269531s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.57151961326599s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6936416625976562s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.41364240646362305s
Security | Sign check for Bio2RDF::Mesh took 0.25313782691955566s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 12.334766626358032s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 1.0270226001739502s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.700920104980469e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-mesh took 1072.427664756775s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.46227598190307617s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006198883056640625s
Extra | Recovery of all triples for Bio2RDF::Mgi took 37.044039487838745s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2858211994171143s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.79459595680237s
Interoperability | New terms check for Bio2RDF::Mgi took 40.91017031669617s
Versatility | Languages check for Bio2RDF::Mgi took 60.24926161766052s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.266862154006958s
Security | Check HTTPS for Bio2RDF::Mgi took 0.14899945259094238s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.9121527671813965s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.37851881980895996s
Availability | RDF dump link check for Bio2RDF::Mgi took 6.286798000335693s
License | MR license check for Bio2RDF::Mgi took 0.5396511554718018s
License | HR license check for Bio2RDF::Mgi took 60.24254393577576s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.29330992698669434s
Understandability | Number of label check for Bio2RDF::Mgi took 10.275437116622925s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5836231708526611s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2715170383453369s
Verifiability | Authors check for Bio2RDF::Mgi took 0.26615071296691895s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2524237632751465s
Performance | Throughput check for Bio2RDF::Mgi took 11.123015642166138s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 72.68909859657288s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.5746824741363525s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.36642980575561523s
Interlinking | skos check for Bio2RDF::Mgi took 0.8632979393005371s
Interlinking | skos check for Bio2RDF::Mgi took 0.3504371643066406s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2959256172180176s
Currency | Creation date check for Bio2RDF::Mgi took 0.5290036201477051s
Currency | Modification date check for Bio2RDF::Mgi took 0.5115017890930176s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 120.50354385375977s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.42264246940612793s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2792501449584961s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.3010094165802002s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 19.314606428146362s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8973171710968018s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6899714469909668s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.4066600799560547s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 70.64219975471497s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.466003179550171s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 11.342693090438843s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3422789573669434s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.583040714263916s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.718768835067749s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.45770740509033203s
Security | Sign check for Bio2RDF::Mgi took 0.2728703022003174s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 12.576343774795532s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.8844375610351562s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.799003601074219e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-mgi took 1074.1675689220428s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.5966184139251709s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005943775177001953s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 35.88780379295349s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2882306575775146s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.88650822639465s
Interoperability | New terms check for Bio2RDF::Ncbigene took 42.7244918346405s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.25389528274536s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2781636714935303s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.14661312103271484s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.7707855701446533s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3505394458770752s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 6.352966070175171s
License | MR license check for Bio2RDF::Ncbigene took 0.4526665210723877s
License | HR license check for Bio2RDF::Ncbigene took 60.253939628601074s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.27292394638061523s
Understandability | Number of label check for Bio2RDF::Ncbigene took 11.190560579299927s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.6068918704986572s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.274855375289917s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2843446731567383s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.26869750022888184s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.049456357955933s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 72.73323845863342s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.32403135299682617s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3766472339630127s
Interlinking | skos check for Bio2RDF::Ncbigene took 1.117487907409668s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.35930585861206055s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2805502414703369s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.583226203918457s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5361464023590088s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 122.27622747421265s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4580414295196533s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2894458770751953s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.288480281829834s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 18.737438917160034s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.891305685043335s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6648406982421875s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.48355698585510254s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 71.02410817146301s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 3.3892407417297363s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 12.440438032150269s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.309389591217041s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.576523780822754s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7000477313995361s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.45186305046081543s
Security | Sign check for Bio2RDF::Ncbigene took 0.28998517990112305s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 12.689324855804443s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.9903779029846191s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011301040649414062s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1081.26811003685s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.5024716854095459s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0003936290740966797s
Extra | Recovery of all triples for Bio2RDF::Ndc took 35.93378043174744s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.3033761978149414s
Amount of data | Number of triples check for Bio2RDF::Ndc took 43.863484621047974s
Interoperability | New terms check for Bio2RDF::Ndc took 41.386165380477905s
Versatility | Languages check for Bio2RDF::Ndc took 60.244505882263184s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.26110267639160156s
Security | Check HTTPS for Bio2RDF::Ndc took 0.16809582710266113s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.9393589496612549s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.3637831211090088s
Availability | RDF dump link check for Bio2RDF::Ndc took 6.415231943130493s
License | MR license check for Bio2RDF::Ndc took 0.48172903060913086s
License | HR license check for Bio2RDF::Ndc took 60.2604546546936s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2742025852203369s
Understandability | Number of label check for Bio2RDF::Ndc took 10.50215196609497s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5984086990356445s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.28626513481140137s
Verifiability | Authors check for Bio2RDF::Ndc took 0.26584696769714355s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2517812252044678s
Performance | Throughput check for Bio2RDF::Ndc took 11.228077411651611s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 78.09884786605835s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.6013352870941162s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.38071632385253906s
Interlinking | skos check for Bio2RDF::Ndc took 0.8090841770172119s
Interlinking | skos check for Bio2RDF::Ndc took 0.36403894424438477s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.28185558319091797s
Currency | Creation date check for Bio2RDF::Ndc took 0.5137670040130615s
Currency | Modification date check for Bio2RDF::Ndc took 0.5059702396392822s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 123.13682627677917s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.43558621406555176s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2959451675415039s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.27936673164367676s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 18.60463809967041s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8940739631652832s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6654708385467529s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.42180323600769043s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 70.37012934684753s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4756717681884766s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 11.781877756118774s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3019030094146729s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.557499408721924s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7208383083343506s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.46451592445373535s
Security | Sign check for Bio2RDF::Ndc took 0.2948935031890869s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 12.87364935874939s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 1.378164291381836s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.76837158203125e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-ndc took 1074.4834196567535s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.6991512775421143s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-netpath took 6.089988946914673s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13215065002441406s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.26793813705444336s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-nextprot took 4.663736343383789s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4739553928375244s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006647109985351562s
Extra | Recovery of all triples for Bio2RDF::Omim took 35.1793487071991s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.3287851810455322s
Amount of data | Number of triples check for Bio2RDF::Omim took 43.996469497680664s
Interoperability | New terms check for Bio2RDF::Omim took 45.5689058303833s
Versatility | Languages check for Bio2RDF::Omim took 60.236040353775024s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2642817497253418s
Security | Check HTTPS for Bio2RDF::Omim took 0.15680956840515137s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.8371412754058838s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.34917664527893066s
Availability | RDF dump link check for Bio2RDF::Omim took 6.373273611068726s
License | MR license check for Bio2RDF::Omim took 0.44696927070617676s
License | HR license check for Bio2RDF::Omim took 60.26158142089844s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2668571472167969s
Understandability | Number of label check for Bio2RDF::Omim took 10.138515949249268s
Understandability | URI regex check for Bio2RDF::Omim took 0.5577282905578613s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2764558792114258s
Verifiability | Authors check for Bio2RDF::Omim took 0.2839510440826416s
Verifiability | Publishers check for Bio2RDF::Omim took 0.26367855072021484s
Performance | Throughput check for Bio2RDF::Omim took 11.093427658081055s
Amount of data | Check the number of entities for Bio2RDF::Omim took 82.86974596977234s
Verifiability | Contribs. check for Bio2RDF::Omim took 2.070619583129883s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3636441230773926s
Interlinking | skos check for Bio2RDF::Omim took 0.7782115936279297s
Interlinking | skos check for Bio2RDF::Omim took 0.35663557052612305s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.27485084533691406s
Currency | Creation date check for Bio2RDF::Omim took 0.5267210006713867s
Currency | Modification date check for Bio2RDF::Omim took 0.5489230155944824s
Rep.Conc. | URIs length for Bio2RDF::Omim took 120.3321578502655s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4138474464416504s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2739989757537842s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.27591753005981445s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 17.221977472305298s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8961813449859619s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6629493236541748s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.41552114486694336s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 71.03231453895569s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.432276964187622s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 12.235422372817993s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3171477317810059s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.53675651550293s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.6996970176696777s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.4446127414703369s
Security | Sign check for Bio2RDF::Omim took 0.2758796215057373s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 11.30636477470398s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.9850094318389893s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00012803077697753906s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-omim took 1076.4548966884613s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.57763671875e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2783544063568115s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.1961669921875e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 3.7156503200531006s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.47074055671691895s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0007107257843017578s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 37.30988550186157s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2747795581817627s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 44.39136624336243s
Interoperability | New terms check for Bio2RDF::Orphanet took 42.06263208389282s
Versatility | Languages check for Bio2RDF::Orphanet took 60.2444543838501s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.2720925807952881s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.1583843231201172s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.7255980968475342s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.3356950283050537s
Availability | RDF dump link check for Bio2RDF::Orphanet took 6.269451379776001s
License | MR license check for Bio2RDF::Orphanet took 0.5576419830322266s
License | HR license check for Bio2RDF::Orphanet took 60.22995638847351s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2739887237548828s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.665875673294067s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5959219932556152s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.28075289726257324s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2666053771972656s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.27834224700927734s
Performance | Throughput check for Bio2RDF::Orphanet took 11.123671054840088s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 78.1451506614685s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.26956653594970703s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.33993959426879883s
Interlinking | skos check for Bio2RDF::Orphanet took 0.9017713069915771s
Interlinking | skos check for Bio2RDF::Orphanet took 0.332444429397583s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.28942012786865234s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5196945667266846s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5307128429412842s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 121.78766417503357s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.46137189865112305s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.28006768226623535s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2787954807281494s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 18.085609912872314s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8994042873382568s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6690824031829834s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.3987123966217041s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 71.72474217414856s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.5969643592834473s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 11.80420994758606s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3564629554748535s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.58806347846985s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.69891357421875s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.44110703468322754s
Security | Sign check for Bio2RDF::Orphanet took 0.2761712074279785s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 12.887306690216064s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.8493781089782715s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.58306884765625e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1079.8300235271454s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13317084312438965s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.711247444152832s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.019882678985595703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.735081672668457s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.47258639335632324s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006387233734130859s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 36.04738759994507s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.276062250137329s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 43.925989627838135s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 44.89351749420166s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.245012521743774s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2637135982513428s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.14722514152526855s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.8561460971832275s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.37127137184143066s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 6.3155786991119385s
License | MR license check for Bio2RDF::Pharmgkb took 0.4987144470214844s
License | HR license check for Bio2RDF::Pharmgkb took 60.24899458885193s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.28445982933044434s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.1945219039917s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5868947505950928s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.27402186393737793s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2860407829284668s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.26438140869140625s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.078173637390137s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 76.29347848892212s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.27263760566711426s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.3496556282043457s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.9561028480529785s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.33188915252685547s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2647240161895752s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5164291858673096s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.49700093269348145s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 120.97688126564026s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4102766513824463s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2871558666229248s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.29488635063171387s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 18.472400903701782s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8977587223052979s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6723880767822266s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4387965202331543s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 70.20326924324036s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.598663806915283s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 11.66691541671753s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3171441555023193s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.550947427749634s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.70304274559021s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4339168071746826s
Security | Sign check for Bio2RDF::Pharmgkb took 0.26087164878845215s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 11.589996576309204s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.3623807430267334s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.2479248046875e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1077.3171169757843s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2579073905944824s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.74588942527771s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.2726771831512451s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.021364212036132812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pid took 3.439558506011963s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2740511894226074s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.3248069286346436s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.494060754776001s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006639957427978516s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 36.51782560348511s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2240321636199951s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.1223247051239s
Interoperability | New terms check for Bio2RDF::Pubmed took 43.0563759803772s
Versatility | Languages check for Bio2RDF::Pubmed took 60.27132534980774s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2781054973602295s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.16687965393066406s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 1.0582504272460938s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3676290512084961s
Availability | RDF dump link check for Bio2RDF::Pubmed took 6.353727340698242s
License | MR license check for Bio2RDF::Pubmed took 0.49195313453674316s
License | HR license check for Bio2RDF::Pubmed took 60.24049997329712s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.25962328910827637s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.763983249664307s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6244826316833496s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2795426845550537s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.28989481925964355s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.25908827781677246s
Performance | Throughput check for Bio2RDF::Pubmed took 11.154784917831421s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 79.52010464668274s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.596869707107544s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.375730037689209s
Interlinking | skos check for Bio2RDF::Pubmed took 0.9041352272033691s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3473515510559082s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2606828212738037s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5386629104614258s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5467660427093506s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 120.10406136512756s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.45342397689819336s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.28957056999206543s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2785806655883789s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 18.425269603729248s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.895054817199707s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6686787605285645s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.4020979404449463s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 70.03091096878052s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4092042446136475s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 12.527250528335571s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3190326690673828s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.618088483810425s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7210338115692139s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.43087053298950195s
Security | Sign check for Bio2RDF::Pubmed took 0.28283166885375977s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 11.758247137069702s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.9647140502929688s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.0202028751373291s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013494491577148438s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1072.176706790924s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.27149510383605957s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.02019500732421875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.224082946777344e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-reactome took 4.296431541442871s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.3392181396484375e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.2596726417541504s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.435943603515625e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-rhea took 4.226292133331299s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.9396178722381592s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.27722668647766113s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.772445678710938e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-sabiork took 9.97716999053955s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.48577213287353516s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006222724914550781s
Extra | Recovery of all triples for Bio2RDF::Sgd took 36.17415952682495s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2544658184051514s
Amount of data | Number of triples check for Bio2RDF::Sgd took 44.586649656295776s
Interoperability | New terms check for Bio2RDF::Sgd took 44.69019436836243s
Versatility | Languages check for Bio2RDF::Sgd took 60.2581090927124s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2517714500427246s
Security | Check HTTPS for Bio2RDF::Sgd took 0.154069185256958s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.8366737365722656s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.35419344902038574s
Availability | RDF dump link check for Bio2RDF::Sgd took 6.350857257843018s
License | MR license check for Bio2RDF::Sgd took 0.5194737911224365s
License | HR license check for Bio2RDF::Sgd took 60.25254845619202s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.28781771659851074s
Understandability | Number of label check for Bio2RDF::Sgd took 10.209333896636963s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5960195064544678s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.27031469345092773s
Verifiability | Authors check for Bio2RDF::Sgd took 0.3017277717590332s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.27643513679504395s
Performance | Throughput check for Bio2RDF::Sgd took 10.636168479919434s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 81.36759829521179s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.7220873832702637s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3458995819091797s
Interlinking | skos check for Bio2RDF::Sgd took 0.7914624214172363s
Interlinking | skos check for Bio2RDF::Sgd took 0.3515024185180664s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2722628116607666s
Currency | Creation date check for Bio2RDF::Sgd took 0.5269005298614502s
Currency | Modification date check for Bio2RDF::Sgd took 0.5398170948028564s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 122.79002332687378s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.42771100997924805s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2868812084197998s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.28452324867248535s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 18.777256965637207s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.89650559425354s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6684539318084717s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4245474338531494s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 70.89968681335449s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4566075801849365s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 12.381333589553833s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3070399761199951s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.538968563079834s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.6958045959472656s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4120209217071533s
Security | Sign check for Bio2RDF::Sgd took 0.2640514373779297s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 11.929104328155518s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 1.0000858306884766s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011277198791503906s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-sgd took 1080.4906585216522s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.410743713378906e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.7289392948150635s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02002882957458496s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0006732940673828125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.5762786865234375e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 4.619917631149292s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.4587898254394531s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0005903244018554688s
Extra | Recovery of all triples for Bio2RDF::Sider took 38.12185788154602s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2662575244903564s
Amount of data | Number of triples check for Bio2RDF::Sider took 44.058311223983765s
Interoperability | New terms check for Bio2RDF::Sider took 43.69907879829407s
Versatility | Languages check for Bio2RDF::Sider took 60.25672459602356s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2723350524902344s
Security | Check HTTPS for Bio2RDF::Sider took 0.15798139572143555s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.2905113697052002s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.33187365531921387s
Availability | RDF dump link check for Bio2RDF::Sider took 6.319667339324951s
License | MR license check for Bio2RDF::Sider took 0.4536867141723633s
License | HR license check for Bio2RDF::Sider took 60.256791830062866s
Amount of data | Number of property check for Bio2RDF::Sider took 0.27832746505737305s
Understandability | Number of label check for Bio2RDF::Sider took 10.584249019622803s
Understandability | URI regex check for Bio2RDF::Sider took 0.5872116088867188s
Understandability | Vocabs check for Bio2RDF::Sider took 0.26195406913757324s
Verifiability | Authors check for Bio2RDF::Sider took 0.28389573097229004s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2736051082611084s
Performance | Throughput check for Bio2RDF::Sider took 11.247421026229858s
Amount of data | Check the number of entities for Bio2RDF::Sider took 75.21224188804626s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.29381799697875977s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3641490936279297s
Interlinking | skos check for Bio2RDF::Sider took 1.0507776737213135s
Interlinking | skos check for Bio2RDF::Sider took 0.3234395980834961s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.29141712188720703s
Currency | Creation date check for Bio2RDF::Sider took 0.5511617660522461s
Currency | Modification date check for Bio2RDF::Sider took 0.5303218364715576s
Rep.Conc. | URIs length for Bio2RDF::Sider took 124.2960216999054s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.419842004776001s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.27824926376342773s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.268965482711792s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 17.13450813293457s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8992893695831299s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6558001041412354s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.4870336055755615s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 70.74614429473877s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.7036242485046387s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 12.12090539932251s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.303044319152832s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.59848427772522s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7130296230316162s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.46186161041259766s
Security | Sign check for Bio2RDF::Sider took 0.30323243141174316s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 12.615410089492798s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.8145828247070312s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0008859634399414062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.863739013671875e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-sider took 1078.571605682373s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.410743713378906e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.26320743560791016s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.504753112792969e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-spike took 6.454803943634033s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.291534423828125e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2695612907409668s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020787477493286133s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.2438507080078125e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-taxon took 2.6025002002716064s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 1.265143632888794s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0005772113800048828s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 35.19260048866272s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2271778583526611s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 44.61568355560303s
Interoperability | New terms check for Bio2RDF::Taxonomy took 42.31725478172302s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.246543645858765s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.27324891090393066s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.15472650527954102s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 1.1120264530181885s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3506021499633789s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 6.4183244705200195s
License | MR license check for Bio2RDF::Taxonomy took 0.5657145977020264s
License | HR license check for Bio2RDF::Taxonomy took 60.231104612350464s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2665865421295166s
Understandability | Number of label check for Bio2RDF::Taxonomy took 11.082656145095825s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5973339080810547s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.269411563873291s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.2704958915710449s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.25502753257751465s
Performance | Throughput check for Bio2RDF::Taxonomy took 10.841140031814575s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 76.58857297897339s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.7914419174194336s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3750741481781006s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.7233681678771973s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.41305971145629883s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.3119685649871826s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5557701587677002s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5328361988067627s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 121.90502619743347s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4434814453125s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2637956142425537s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2880992889404297s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 18.02364706993103s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8907392024993896s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6530084609985352s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.39734530448913574s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 70.90183329582214s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.4243099689483643s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 12.07575249671936s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3222343921661377s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.557963848114014s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7095963954925537s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.41529130935668945s
Security | Sign check for Bio2RDF::Taxonomy took 0.285534143447876s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.836879253387451s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.5473363399505615s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010800361633300781s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1071.542228937149s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.14376258850097656s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.26126790046691895s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020111083984375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.24249267578125e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 18.31025195121765s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4665491580963135s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006527900695800781s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 34.65319609642029s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2472500801086426s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 44.4915337562561s
Interoperability | New terms check for Bio2RDF::Wormbase took 43.360877990722656s
Versatility | Languages check for Bio2RDF::Wormbase took 60.24976181983948s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.26291441917419434s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.17001581192016602s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.7587096691131592s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3293476104736328s
Availability | RDF dump link check for Bio2RDF::Wormbase took 6.4017627239227295s
License | MR license check for Bio2RDF::Wormbase took 0.5468635559082031s
License | HR license check for Bio2RDF::Wormbase took 60.25979709625244s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2840697765350342s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.063963413238525s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.582310676574707s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.25566935539245605s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.28032708168029785s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.28121280670166016s
Performance | Throughput check for Bio2RDF::Wormbase took 10.822239875793457s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 80.12263894081116s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.5986809730529785s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3497891426086426s
Interlinking | skos check for Bio2RDF::Wormbase took 0.8137857913970947s
Interlinking | skos check for Bio2RDF::Wormbase took 0.37661266326904297s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.28508496284484863s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5421574115753174s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5002427101135254s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 121.05678248405457s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4290182590484619s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2906014919281006s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.30672311782836914s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 18.794816732406616s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8943140506744385s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6654407978057861s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.505622386932373s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 70.85601687431335s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.4716598987579346s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 11.767667293548584s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3581721782684326s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.610798835754395s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7108566761016846s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.45564842224121094s
Security | Sign check for Bio2RDF::Wormbase took 0.2893650531768799s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 12.911468505859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 1.327432632446289s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.320808410644531e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1080.2177755832672s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 7.128715515136719e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.2635648250579834s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.0200650691986084s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.2636184692382812e-05s
Believability | Calculation of trust value for Biografías y Vidas took 7.3909759521484375e-06s
INFO | --- Analysis for biografiasyvidas took 4.125635385513306s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.25612568855285645s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.26981568336486816s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.606910705566406e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 5.245208740234375e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.127882242202759s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.279202938079834s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.2901763916015625e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for biolit took 3.4888036251068115s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.38690185546875e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.2521789073944092s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.1961669921875e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 6.67572021484375e-06s
INFO | --- Analysis for biolod-pdb took 7.106740236282349s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6040489673614502s
Availability | VoID file availability check for BioModels RDF took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2824099063873291s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for BioModels RDF took 6.9141387939453125e-06s
INFO | --- Analysis for biomodels-rdf took 4.246575355529785s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.7304587364196777s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0011360645294189453s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2745339870452881s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.218650817871094e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.4373016357421875e-06s
INFO | --- Analysis for Biop took 7.408994436264038s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.315376281738281e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.7189061641693115s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.152557373046875e-06s
INFO | --- Analysis for Bioportal took 2.9827704429626465s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 5.125999450683594e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.26316189765930176s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020247459411621094s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006165504455566406s
Believability | Calculation of trust value for Amphibian gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-aao took 2.6605288982391357s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.2438507080078125e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.26708269119262695s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02646493911743164s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00038743019104003906s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-aba took 2.5831286907196045s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.27223730087280273s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015544891357421875s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-acgt took 2.7535157203674316s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 5.221366882324219e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.26920580863952637s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003247261047363281s
Believability | Calculation of trust value for Animal natural history and life history took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-adw took 2.6139698028564453s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 5.602836608886719e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.27192258834838867s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02024674415588379s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00046944618225097656s
Believability | Calculation of trust value for Anatomical Entity Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aeo took 2.7090561389923096s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.27167415618896484s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.019949913024902344s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009469985961914062s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aero took 2.6537411212921143s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.172325134277344e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.260298490524292s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020180940628051758s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00039124488830566406s
Believability | Calculation of trust value for AI/RHEUM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-air took 2.648817777633667s
Availability | SPARQL endpoint availability check for Amino Acid took 4.982948303222656e-05s
Availability | VoID file availability check for Amino Acid took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.27857208251953125s
Reputation | Calculation of the PageRank for Amino Acid took 0.02010488510131836s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002465248107910156s
Believability | Calculation of trust value for Amino Acid took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.6348586082458496s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.27157092094421387s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020027875900268555s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.000274658203125s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-apo took 2.7053420543670654s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.220008850097656e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.26187705993652344s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02011561393737793s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00023031234741210938s
Believability | Calculation of trust value for African Traditional Medicine took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-atmo took 2.6206250190734863s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2715322971343994s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020095109939575195s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.58306884765625e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ato took 2.5957443714141846s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.24021172523498535s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020189285278320312s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013518333435058594s
Believability | Calculation of trust value for BioAssay Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bao took 2.6519672870635986s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2850182056427002s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003802776336669922s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.745131492614746s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 6.651878356933594e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.26537036895751953s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020207881927490234s
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.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003292560577392578s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bcgo took 2.6570141315460205s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2562286853790283s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0008697509765625s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0015680789947509766s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bdo took 2.6532747745513916s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.27326250076293945s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.00048613548278808594s
Believability | Calculation of trust value for Basic Formal Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bfo took 2.6026597023010254s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.458427429199219e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2622263431549072s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007207393646240234s
Believability | Calculation of trust value for Bleeding History Phenotype took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bho took 2.6443750858306885s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.24912667274475098s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020322799682617188s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004405975341796875s
Believability | Calculation of trust value for Bilateria anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bila took 2.5873420238494873s
Availability | SPARQL endpoint availability check for BIRNLex took 4.38690185546875e-05s
Availability | VoID file availability check for BIRNLex took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.24828672409057617s
Reputation | Calculation of the PageRank for BIRNLex took 0.02081775665283203s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014863014221191406s
Believability | Calculation of trust value for BIRNLex took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-birnlex took 2.6198668479919434s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.26105380058288574s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007386207580566406s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.503633737564087s
Availability | SPARQL endpoint availability check for BioPAX took 4.291534423828125e-05s
Availability | VoID file availability check for BioPAX took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for BioPAX took 0.24254107475280762s
Reputation | Calculation of the PageRank for BioPAX took 0.020197391510009766s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.72747802734375e-05s
Believability | Calculation of trust value for BioPAX took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bp took 2.629127025604248s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2968463897705078s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020167827606201172s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003254413604736328s
Believability | Calculation of trust value for Biomedical Resource Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.5806827545166016s
Availability | SPARQL endpoint availability check for Spatial Ontology took 7.62939453125e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.26703715324401855s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00020647048950195312s
Believability | Calculation of trust value for Spatial Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-bspo took 2.6821281909942627s
Availability | SPARQL endpoint availability check for BioTop took 4.2438507080078125e-05s
Availability | VoID file availability check for BioTop took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for BioTop took 0.2581603527069092s
Reputation | Calculation of the PageRank for BioTop took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006515979766845703s
Believability | Calculation of trust value for BioTop took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bt took 2.643902540206909s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.2438507080078125e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.26850366592407227s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008862018585205078s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-bto took 2.6258363723754883s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3117823600769043s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.001804351806640625s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-canco took 3.021721124649048s
Availability | SPARQL endpoint availability check for CAO took 4.267692565917969e-05s
Availability | VoID file availability check for CAO took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for CAO took 0.25078630447387695s
Reputation | Calculation of the PageRank for CAO took 0.020199060440063477s
Interlinking | Calculation of Degree of Connection for CAO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006089210510253906s
Believability | Calculation of trust value for CAO took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cao took 2.5388717651367188s
Availability | SPARQL endpoint availability check for CareLex took 4.315376281738281e-05s
Availability | VoID file availability check for CareLex took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for CareLex took 0.2718088626861572s
Reputation | Calculation of the PageRank for CareLex took 0.020107269287109375s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.673004150390625e-05s
Believability | Calculation of trust value for CareLex took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-carelex took 2.6198298931121826s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2538940906524658s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02025151252746582s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007922649383544922s
Believability | Calculation of trust value for Cell Cycle Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cco took 2.5161962509155273s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0004036426544189453s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.24541687965393066s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.019942045211791992s
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.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025653839111328125s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cdao took 2.489368200302124s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.2438507080078125e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2475724220275879s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007681846618652344s
Believability | Calculation of trust value for Chemical entities of biological interest took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-chebi took 2.5802388191223145s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.4345855712890625e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.2694220542907715s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002536773681640625s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.5867927074432373s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.28964734077453613s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020112276077270508s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007481575012207031s
Believability | Calculation of trust value for Chemical Information Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cheminf took 2.5301733016967773s
Availability | SPARQL endpoint availability check for Cell type took 5.7697296142578125e-05s
Availability | VoID file availability check for Cell type took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Cell type took 0.2830333709716797s
Reputation | Calculation of the PageRank for Cell type took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00038123130798339844s
Believability | Calculation of trust value for Cell type took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cl took 2.64487886428833s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.26979827880859375s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008280277252197266s
Believability | Calculation of trust value for Cell Line Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-clo took 2.626479148864746s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2648024559020996s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017452239990234375s
Believability | Calculation of trust value for Clinical Measurement Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cmo took 2.620366334915161s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 6.222724914550781e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.2590627670288086s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.0202786922454834s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.000209808349609375s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-cno took 2.601813793182373s
Availability | SPARQL endpoint availability check for Wheat trait took 4.410743713378906e-05s
Availability | VoID file availability check for Wheat trait took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.2651357650756836s
Reputation | Calculation of the PageRank for Wheat trait took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 6.4849853515625e-05s
Believability | Calculation of trust value for Wheat trait took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.646129608154297s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.887580871582031e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.28334641456604004s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003402233123779297s
Believability | Calculation of trust value for Cognitive Atlas took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-cogat took 2.592005491256714s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.26860785484313965s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007503032684326172s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cogpo took 2.655200481414795s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 5.459785461425781e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2707479000091553s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00048041343688964844s
Believability | Calculation of trust value for Current Procedural Terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cpt took 2.5998666286468506s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.2438507080078125e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.34626150131225586s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020293712615966797s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.001729726791381836s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-csp took 3.0911366939544678s
Availability | SPARQL endpoint availability check for COSTART took 4.410743713378906e-05s
Availability | VoID file availability check for COSTART took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for COSTART took 0.298292875289917s
Reputation | Calculation of the PageRank for COSTART took 0.02013683319091797s
Interlinking | Calculation of Degree of Connection for COSTART took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for COSTART took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009655952453613281s
Believability | Calculation of trust value for COSTART took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cst took 2.593163013458252s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.172325134277344e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0003185272216796875s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.27608680725097656s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020033597946166992s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005171298980712891s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ctcae took 2.6114797592163086s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.267692565917969e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2505357265472412s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004417896270751953s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ctx took 2.5806586742401123s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.1961669921875e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2627561092376709s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020282268524169922s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00030159950256347656s
Believability | Calculation of trust value for Dendritic cell took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.612708806991577s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 9.131431579589844e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.24106907844543457s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02018260955810547s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 0.00010514259338378906s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ddanat took 2.680830955505371s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.410743713378906e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2628154754638672s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.01998615264892578s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009238719940185547s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ddi took 2.594452142715454s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2750520706176758s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.869171142578125e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.528339147567749s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.258040189743042s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001633167266845703s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.5513367652893066s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Human disease ontology took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2719602584838867s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02005934715270996s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006248950958251953s
Believability | Calculation of trust value for Human disease ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-doid took 2.6523563861846924s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.24448370933532715s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008378028869628906s
Believability | Calculation of trust value for Electrocardiography Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ecg took 2.5840587615966797s
Availability | SPARQL endpoint availability check for Evidence codes took 4.267692565917969e-05s
Availability | VoID file availability check for Evidence codes took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2686169147491455s
Reputation | Calculation of the PageRank for Evidence codes took 0.02016615867614746s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.0040740966796875e-05s
Believability | Calculation of trust value for Evidence codes took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-eco took 2.6208109855651855s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3282761573791504s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017323493957519531s
Believability | Calculation of trust value for Experimental Factor Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-efo took 3.1522436141967773s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.291534423828125e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2713449001312256s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.001149892807006836s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ehda took 2.5715174674987793s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.267692565917969e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.24267816543579102s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020231962203979492s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007061958312988281s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.634490728378296s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.3392181396484375e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.2644996643066406s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.021184921264648438s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005300045013427734s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.6572682857513428s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 6.747245788574219e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.25141119956970215s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020135164260864258s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.86102294921875e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-emap took 2.582498550415039s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2686300277709961s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00038886070251464844s
Believability | Calculation of trust value for Environment Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-envo took 2.601261854171753s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.506111145019531e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.25574302673339844s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020628690719604492s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002982616424560547s
Believability | Calculation of trust value for Plant environmental conditions took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-eo took 2.6780450344085693s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 5.53131103515625e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.263810396194458s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.00119781494140625s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ep took 2.6505966186523438s
Availability | SPARQL endpoint availability check for Epilepsy took 4.267692565917969e-05s
Availability | VoID file availability check for Epilepsy took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.26126623153686523s
Reputation | Calculation of the PageRank for Epilepsy took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001354217529296875s
Believability | Calculation of trust value for Epilepsy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.661041498184204s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.458427429199219e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2642202377319336s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011298656463623047s
Believability | Calculation of trust value for eagle-i research resource ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ero took 2.6143527030944824s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.1961669921875e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.26952290534973145s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011076927185058594s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ev took 2.591658592224121s
Availability | SPARQL endpoint availability check for ExO took 4.410743713378906e-05s
Availability | VoID file availability check for ExO took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for ExO took 0.2601284980773926s
Reputation | Calculation of the PageRank for ExO took 0.02022266387939453s
Interlinking | Calculation of Degree of Connection for ExO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002372264862060547s
Believability | Calculation of trust value for ExO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-exo took 2.5475363731384277s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 5.8650970458984375e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2811903953552246s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011134147644042969s
Believability | Calculation of trust value for Fungal gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fao took 2.62410569190979s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.291534423828125e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2697916030883789s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02023482322692871s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00018405914306640625s
Believability | Calculation of trust value for Biological imaging methods took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbbi took 2.565337896347046s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.6253204345703125e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2593271732330322s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006487369537353516s
Believability | Calculation of trust value for Drosophila gross anatomy took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-fbbt took 2.6752727031707764s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.2438507080078125e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2811291217803955s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004210472106933594s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbcv took 2.5940134525299072s
Availability | SPARQL endpoint availability check for Drosophila development took 4.5299530029296875e-05s
Availability | VoID file availability check for Drosophila development took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2592282295227051s
Reputation | Calculation of the PageRank for Drosophila development took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.76837158203125e-05s
Believability | Calculation of trust value for Drosophila development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fbdv took 2.7037298679351807s
Availability | SPARQL endpoint availability check for Fly taxonomy took 5.7220458984375e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2640986442565918s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020302772521972656s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003657341003417969s
Believability | Calculation of trust value for Fly taxonomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbsp took 2.5144083499908447s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.76837158203125e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2741248607635498s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002181529998779297s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.677180051803589s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2603588104248047s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004203319549560547s
Believability | Calculation of trust value for Family Health History Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fhho took 2.645846366882324s
Availability | SPARQL endpoint availability check for Influenza Ontology took 8.20159912109375e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.25670433044433594s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020223617553710938s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010349750518798828s
Believability | Calculation of trust value for Influenza Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-flu took 2.66866397857666s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.26908278465270996s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.198883056640625e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fma took 2.648923397064209s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.260225772857666s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001277923583984375s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fypo took 2.646942615509033s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.27399420738220215s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02013874053955078s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.202957153320312e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-geospecies took 2.6372175216674805s
Availability | SPARQL endpoint availability check for General Formal Ontology took 6.341934204101562e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.28214502334594727s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.000164031982421875s
Believability | Calculation of trust value for General Formal Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gfo took 2.53397798538208s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.649162292480469e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.30005908012390137s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006666183471679688s
Believability | Calculation of trust value for General Formal Ontology: Biology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.651174306869507s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.291534423828125e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0012881755828857422s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2438497543334961s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008769035339355469s
Believability | Calculation of trust value for Gene Ontology Extension took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.518833637237549s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Gene Ontology took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.27910757064819336s
Reputation | Calculation of the PageRank for Gene Ontology took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008571147918701172s
Believability | Calculation of trust value for Gene Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.5178983211517334s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.267692565917969e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2719447612762451s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02037835121154785s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.9802322387695312e-05s
Believability | Calculation of trust value for Cereal Plant Development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gro took 2.675051212310791s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 7.05718994140625e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2493283748626709s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020328521728515625s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004482269287109375s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.5354442596435547s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2603275775909424s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020628690719604492s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007240772247314453s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.628868341445923s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2586939334869385s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005903244018554688s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hao took 2.5969932079315186s
Availability | SPARQL endpoint availability check for HCPCS took 0.0004100799560546875s
Availability | VoID file availability check for HCPCS took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for HCPCS took 0.25298380851745605s
Reputation | Calculation of the PageRank for HCPCS took 0.020145416259765625s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002181529998779297s
Believability | Calculation of trust value for HCPCS took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.5590014457702637s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.57763671875e-05s
Availability | VoID file availability check for Health Level Seven took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.27246856689453125s
Reputation | Calculation of the PageRank for Health Level Seven took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.001264333724975586s
Believability | Calculation of trust value for Health Level Seven took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hl7 took 2.6459827423095703s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 9.751319885253906e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.26322197914123535s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00034737586975097656s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.5918967723846436s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2614607810974121s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 2.956390380859375e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hom took 2.7008461952209473s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 5.2928924560546875e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.27155303955078125s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.02013087272644043s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.956390380859375e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.6527254581451416s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.27158308029174805s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.02017498016357422s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006361007690429688s
Believability | Calculation of trust value for Human Phenotype Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.5491297245025635s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.27125978469848633s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020392656326293945s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010128021240234375s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hpio took 2.561189889907837s
Availability | SPARQL endpoint availability check for HUGO took 4.315376281738281e-05s
Availability | VoID file availability check for HUGO took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for HUGO took 0.2684488296508789s
Reputation | Calculation of the PageRank for HUGO took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for HUGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.796287536621094e-05s
Believability | Calculation of trust value for HUGO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hugo took 2.661435604095459s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 5.602836608886719e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.2674410343170166s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020083904266357422s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006580352783203125s
Believability | Calculation of trust value for Information Artifact Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-iao took 2.6474406719207764s
Availability | SPARQL endpoint availability check for ICD10 took 4.38690185546875e-05s
Availability | VoID file availability check for ICD10 took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for ICD10 took 0.2730991840362549s
Reputation | Calculation of the PageRank for ICD10 took 0.02011251449584961s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008070468902587891s
Believability | Calculation of trust value for ICD10 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10 took 2.6224422454833984s
Availability | SPARQL endpoint availability check for ICD10CM took 0.0005946159362792969s
Availability | VoID file availability check for ICD10CM took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.2599661350250244s
Reputation | Calculation of the PageRank for ICD10CM took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.000629425048828125s
Believability | Calculation of trust value for ICD10CM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.5940921306610107s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.696846008300781e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.24496841430664062s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.0001862049102783203s
Believability | Calculation of trust value for ICD-10-PCS took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.5670230388641357s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.4345855712890625e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0010783672332763672s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.27385401725769043s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0009894371032714844s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0007622241973876953s
Believability | Calculation of trust value for International Classification of Diseases took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.6348884105682373s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.363059997558594e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.25875282287597656s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020339488983154297s
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.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004477500915527344s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.603703498840332s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2728886604309082s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012319087982177734s
Believability | Calculation of trust value for International Classification for Nursing Practice took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icnp took 2.6330385208129883s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.26834654808044434s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004355907440185547s
Believability | Calculation of trust value for International Classification of Primary Care took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icpc took 2.617161989212036s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 5.1021575927734375e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.25374722480773926s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008828639984130859s
Believability | Calculation of trust value for ICPC-2 PLUS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.6181910037994385s
Availability | SPARQL endpoint availability check for ICPS Network took 4.3392181396484375e-05s
Availability | VoID file availability check for ICPS Network took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2539854049682617s
Reputation | Calculation of the PageRank for ICPS Network took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002193450927734375s
Believability | Calculation of trust value for ICPS Network took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icps took 2.6324548721313477s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 5.030632019042969e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.27304506301879883s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02035069465637207s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008749961853027344s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ido took 2.5896828174591064s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.26097536087036133s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020172595977783203s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011591911315917969s
Believability | Calculation of trust value for Brucellosis Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-idobru took 2.642690658569336s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.26688146591186523s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.02589106559753418s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0008566379547119141s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0014004707336425781s
Believability | Calculation of trust value for Malaria Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-idomal took 2.6570286750793457s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.291534423828125e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.3359813690185547s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02007293701171875s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003101825714111328s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-iev took 2.5850892066955566s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.8160552978515625e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2534961700439453s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015091896057128906s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-imgt took 2.5988311767578125s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.458427429199219e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.27412986755371094s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020092487335205078s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005235671997070312s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-imr took 2.568727970123291s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2714242935180664s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020223617553710938s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008246898651123047s
Believability | Calculation of trust value for Interaction Network Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ino took 2.758704423904419s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 7.009506225585938e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2652862071990967s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.0040740966796875e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.601208448410034s
Availability | SPARQL endpoint availability check for IxnO took 4.7206878662109375e-05s
Availability | VoID file availability check for IxnO took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for IxnO took 0.2713046073913574s
Reputation | Calculation of the PageRank for IxnO took 0.020273208618164062s
Interlinking | Calculation of Degree of Connection for IxnO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0001900196075439453s
Believability | Calculation of trust value for IxnO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ixno took 2.6308681964874268s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.458427429199219e-05s
Availability | VoID file availability check for SysMO-JERM took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.27396678924560547s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003910064697265625s
Believability | Calculation of trust value for SysMO-JERM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-jerm took 2.631903886795044s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 6.198883056640625e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.27722740173339844s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.6716461181640625e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-kisao took 2.708451271057129s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.5299530029296875e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.25715184211730957s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020253658294677734s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00021004676818847656s
Believability | Calculation of trust value for Loggerhead nesting took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-lhn took 2.6078603267669678s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Lipid Ontology took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.26423096656799316s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020090579986572266s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020265579223632812s
Believability | Calculation of trust value for Lipid Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-lipro took 2.514096975326538s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.38690185546875e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.33452510833740234s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.001828908920288086s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-lnc took 3.066333770751953s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2713644504547119s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006711483001708984s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ma took 2.591902256011963s
Availability | SPARQL endpoint availability check for Multiple alignment took 6.961822509765625e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.253063440322876s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00020766258239746094s
Believability | Calculation of trust value for Multiple alignment took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mao took 2.6624650955200195s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.458427429199219e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2772996425628662s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007007122039794922s
Believability | Calculation of trust value for Minimal anatomical terminology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mat took 2.651277542114258s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.482269287109375e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.26102447509765625s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020071744918823242s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004451274871826172s
Believability | Calculation of trust value for Breast tissue cell lines took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.5918989181518555s
Availability | SPARQL endpoint availability check for Cell line ontology took 0.0006337165832519531s
Availability | VoID file availability check for Cell line ontology took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.25818943977355957s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020255088806152344s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007512569427490234s
Believability | Calculation of trust value for Cell line ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mccl took 2.557681083679199s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2857811450958252s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021509647369384766s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0015001296997070312s
Believability | Calculation of trust value for Cell line ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.6749894618988037s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.315376281738281e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.28316569328308105s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020124435424804688s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00025653839111328125s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mcv took 2.6246824264526367s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.315376281738281e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2471482753753662s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.019927024841308594s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00016880035400390625s
Believability | Calculation of trust value for Master Drug Data Base took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-mddb took 2.6277143955230713s
Availability | SPARQL endpoint availability check for MedDRA took 0.0006020069122314453s
Availability | VoID file availability check for MedDRA took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2598612308502197s
Reputation | Calculation of the PageRank for MedDRA took 0.020099639892578125s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011196136474609375s
Believability | Calculation of trust value for MedDRA took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mdr took 2.619497537612915s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.38690185546875e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2589905261993408s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009036064147949219s
Believability | Calculation of trust value for MedlinePlus Health Topics took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.5605995655059814s
Availability | SPARQL endpoint availability check for MeGO took 4.363059997558594e-05s
Availability | VoID file availability check for MeGO took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for MeGO took 0.2904341220855713s
Reputation | Calculation of the PageRank for MeGO took 0.020145654678344727s
Interlinking | Calculation of Degree of Connection for MeGO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001423358917236328s
Believability | Calculation of trust value for MeGO took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mego took 2.644594192504883s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.291534423828125e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3310074806213379s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020301103591918945s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0017931461334228516s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.081162691116333s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.25008440017700195s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020071029663085938s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006012916564941406s
Believability | Calculation of trust value for Mental Functioning Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mf took 2.606332302093506s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.3392181396484375e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.27090907096862793s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02026534080505371s
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.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005640983581542969s
Believability | Calculation of trust value for Medaka fish anatomy and development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mfo took 2.645504951477051s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.29231929779052734s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007574558258056641s
Believability | Calculation of trust value for Emotion Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mfoem took 2.645517110824585s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.29073500633239746s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020104646682739258s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.0001010894775390625s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mhc took 2.632361650466919s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.315376281738281e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.27892136573791504s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.02013683319091797s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006577968597412109s
Believability | Calculation of trust value for Protein-protein interaction took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mi took 2.603508472442627s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.506111145019531e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2608828544616699s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.000705718994140625s
Believability | Calculation of trust value for Mosquito insecticide resistance took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-miro took 2.602001190185547s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.2680051326751709s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02016901969909668s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001308917999267578s
Believability | Calculation of trust value for Measurement Method Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mmo took 2.6357481479644775s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for MGED Ontology took 0.0010657310485839844s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.26268672943115234s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020229339599609375s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003783702850341797s
Believability | Calculation of trust value for MGED Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mo took 2.672776222229004s
Availability | SPARQL endpoint availability check for Protein modification took 4.267692565917969e-05s
Availability | VoID file availability check for Protein modification took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2958822250366211s
Reputation | Calculation of the PageRank for Protein modification took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002346038818359375s
Believability | Calculation of trust value for Protein modification took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mod took 2.64548397064209s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.363059997558594e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.26607656478881836s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020247936248779297s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006337165832519531s
Believability | Calculation of trust value for Mammalian phenotype took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mp took 2.6088898181915283s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.315376281738281e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.256807804107666s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00051116943359375s
Believability | Calculation of trust value for Mouse pathology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mpath took 2.662818670272827s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.291534423828125e-05s
Availability | VoID file availability check for Mass spectrometry took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.25668764114379883s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02015399932861328s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003504753112792969s
Believability | Calculation of trust value for Mass spectrometry took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ms took 2.571587085723877s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.482269287109375e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.30772948265075684s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018367767333984375s
Believability | Calculation of trust value for Medical Subject Headings took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-msh took 3.063659429550171s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.315376281738281e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0011355876922607422s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2576296329498291s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.0200955867767334s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00016999244689941406s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mthch took 2.5731148719787598s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 5.2928924560546875e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.24728894233703613s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0012722015380859375s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0010347366333007812s
Believability | Calculation of trust value for Natural Products Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-natpro took 2.6000640392303467s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 5.0067901611328125e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.3157031536102295s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.021270751953125s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0009703636169433594s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0009520053863525391s
Believability | Calculation of trust value for NCBI organismal classification took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.8864364624023438s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.935264587402344e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3151736259460449s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0019683837890625s
Believability | Calculation of trust value for NCI Thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ncit took 3.0243499279022217s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.458427429199219e-05s
Availability | VoID file availability check for National Drug Data File took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.27767419815063477s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02084946632385254s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006606578826904297s
Believability | Calculation of trust value for National Drug Data File took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-nddf took 2.6454837322235107s
Availability | SPARQL endpoint availability check for National Drug File took 4.38690185546875e-05s
Availability | VoID file availability check for National Drug File took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2657132148742676s
Reputation | Calculation of the PageRank for National Drug File took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012362003326416016s
Believability | Calculation of trust value for National Drug File took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.593153953552246s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.38690185546875e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.24226045608520508s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020050764083862305s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.001138925552368164s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.5979318618774414s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2504854202270508s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020103931427001953s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006496906280517578s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-neomark took 2.6108973026275635s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0004074573516845703s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.27726268768310547s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00011849403381347656s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.494985580444336s
Availability | SPARQL endpoint availability check for NIFSTD took 4.1961669921875e-05s
Availability | VoID file availability check for NIFSTD took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.342057466506958s
Reputation | Calculation of the PageRank for NIFSTD took 0.020184040069580078s
Interlinking | Calculation of Degree of Connection for NIFSTD took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NIFSTD took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018486976623535156s
Believability | Calculation of trust value for NIFSTD took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nif took 3.038100242614746s
Availability | SPARQL endpoint availability check for NIF Cell took 4.3392181396484375e-05s
Availability | VoID file availability check for NIF Cell took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2698097229003906s
Reputation | Calculation of the PageRank for NIF Cell took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.001331329345703125s
Believability | Calculation of trust value for NIF Cell took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.600295305252075s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 6.961822509765625e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.26815009117126465s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0009098052978515625s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0015289783477783203s
Believability | Calculation of trust value for NIF Dysfunction took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.529675245285034s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.26666760444641113s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005471706390380859s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-nigo took 2.623816728591919s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.38690185546875e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2847607135772705s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005583763122558594s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nmr took 2.676492691040039s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2825334072113037s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010514259338378906s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.6396572589874268s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.25482630729675293s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.0205078125s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011715888977050781s
Believability | Calculation of trust value for NanoParticle Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-npo took 2.5818967819213867s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.26694536209106445s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020334482192993164s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007193088531494141s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oae took 2.6184751987457275s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.9591064453125e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.26810264587402344s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.001443624496459961s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-obi took 2.563438892364502s
Availability | SPARQL endpoint availability check for OBOE took 4.3392181396484375e-05s
Availability | VoID file availability check for OBOE took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for OBOE took 0.2822916507720947s
Reputation | Calculation of the PageRank for OBOE took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011730194091796875s
Believability | Calculation of trust value for OBOE took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-oboe took 2.6628406047821045s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.172325134277344e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.27117371559143066s
Reputation | Calculation of the PageRank for OBOE SBC took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007793903350830078s
Believability | Calculation of trust value for OBOE SBC took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.6220903396606445s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 7.462501525878906e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2748756408691406s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005698204040527344s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ocre took 2.7626373767852783s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.27236247062683105s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008404254913330078s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-odgi took 2.602647304534912s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2747468948364258s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0009071826934814453s
Believability | Calculation of trust value for Ontology for Genetic Interval took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ogi took 2.672210693359375s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2474832534790039s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00029969215393066406s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ogmd took 2.575847625732422s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 5.340576171875e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.24701285362243652s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0007328987121582031s
Believability | Calculation of trust value for Ontology for General Medical Science took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ogms took 2.6531801223754883s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.410743713378906e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.25287914276123047s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011475086212158203s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-omim took 2.5465199947357178s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.2723500728607178s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003807544708251953s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-omit took 2.5966415405273438s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2593953609466553s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005984306335449219s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-omrse took 2.458911657333374s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.863739013671875e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.27166032791137695s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020579814910888672s
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.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007748603820800781s
Believability | Calculation of trust value for Ontology of Data Mining took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontodm took 2.690837860107422s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.26976966857910156s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00024366378784179688s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ontodt took 2.63832426071167s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.315376281738281e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2621631622314453s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006148815155029297s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.5669403076171875s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.29225945472717285s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009305477142333984s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-opl took 2.648341655731201s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.220008850097656e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.285250186920166s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.02038407325744629s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.000946044921875s
Believability | Calculation of trust value for Phenotypic quality took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pato took 2.60422945022583s
Availability | SPARQL endpoint availability check for Physician Data Query took 6.818771362304688e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.26144886016845703s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008168220520019531s
Believability | Calculation of trust value for Physician Data Query took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pdq took 2.545355796813965s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.220008850097656e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2843971252441406s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008013248443603516s
Believability | Calculation of trust value for Pediatric Terminology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-pedterm took 2.6629979610443115s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 6.103515625e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2698819637298584s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0001990795135498047s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-peo took 2.6434686183929443s
Availability | SPARQL endpoint availability check for PHARE took 4.220008850097656e-05s
Availability | VoID file availability check for PHARE took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for PHARE took 0.24770689010620117s
Reputation | Calculation of the PageRank for PHARE took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for PHARE took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006258487701416016s
Believability | Calculation of trust value for PHARE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-phare took 2.5586864948272705s
Availability | SPARQL endpoint availability check for PKO_Re took 4.3392181396484375e-05s
Availability | VoID file availability check for PKO_Re took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2611873149871826s
Reputation | Calculation of the PageRank for PKO_Re took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00017118453979492188s
Believability | Calculation of trust value for PKO_Re took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pko took 2.588136911392212s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.267692565917969e-05s
Availability | VoID file availability check for PMA 2010 took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2803335189819336s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020247220993041992s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009217262268066406s
Believability | Calculation of trust value for PMA 2010 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pma took 2.636711835861206s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 5.1975250244140625e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2587165832519531s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02019786834716797s
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.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016641616821289062s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pmr took 2.6907951831817627s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2517061233520508s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020079851150512695s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00038242340087890625s
Believability | Calculation of trust value for Plant Anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-po took 2.5939371585845947s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.267692565917969e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2700212001800537s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.224082946777344e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.5789878368377686s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.27091383934020996s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020239830017089844s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004303455352783203s
Believability | Calculation of trust value for Plant Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.6459059715270996s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.291534423828125e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.26896238327026367s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006740093231201172s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pr took 2.6265780925750732s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.1961669921875e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2566564083099365s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002853870391845703s
Believability | Calculation of trust value for Proteomics data and process provenance took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-propreo took 2.693207263946533s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.25547051429748535s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00014162063598632812s
Believability | Calculation of trust value for Pathway ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pw took 2.6461241245269775s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.24546241760253906s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-qibo took 2.5945839881896973s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.124641418457031e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0010416507720947266s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.29876017570495605s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0018258094787597656s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rcd took 3.0952281951904297s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2688271999359131s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012683868408203125s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rctontology took 2.5632505416870117s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 9.322166442871094e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2710001468658447s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.965896606445312e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-repo took 2.6531693935394287s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.076957702636719e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.26916074752807617s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020375728607177734s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00018644332885742188s
Believability | Calculation of trust value for Physico-chemical process took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rex took 2.6663055419921875s
Availability | SPARQL endpoint availability check for RadLex took 4.76837158203125e-05s
Availability | VoID file availability check for RadLex took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for RadLex took 0.2605702877044678s
Reputation | Calculation of the PageRank for RadLex took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for RadLex took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RadLex took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015749931335449219s
Believability | Calculation of trust value for RadLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rid took 2.59496808052063s
Availability | SPARQL endpoint availability check for RNA ontology took 8.702278137207031e-05s
Availability | VoID file availability check for RNA ontology took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2755591869354248s
Reputation | Calculation of the PageRank for RNA ontology took 0.020154237747192383s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005869865417480469s
Believability | Calculation of trust value for RNA ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-rnao took 2.611217737197876s
Availability | SPARQL endpoint availability check for Role Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Role Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.24976372718811035s
Reputation | Calculation of the PageRank for Role Ontology took 0.020209312438964844s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.0001895427703857422s
Believability | Calculation of trust value for Role Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-roleo took 2.5572619438171387s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 7.963180541992188e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.26662588119506836s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001761913299560547s
Believability | Calculation of trust value for Rat Strain Ontology took 1.5020370483398438e-05s
INFO | --- Analysis for bioportal-rs took 2.638793468475342s
Availability | SPARQL endpoint availability check for RxNORM took 0.00011730194091796875s
Availability | VoID file availability check for RxNORM took 0.000518798828125s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2617635726928711s
Reputation | Calculation of the PageRank for RxNORM took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006303787231445312s
Believability | Calculation of trust value for RxNORM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.6322073936462402s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.410743713378906e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2762782573699951s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010471343994140625s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sao took 2.714339256286621s
Availability | SPARQL endpoint availability check for Systems Biology took 7.319450378417969e-05s
Availability | VoID file availability check for Systems Biology took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2714519500732422s
Reputation | Calculation of the PageRank for Systems Biology took 0.021669864654541016s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0008962154388427734s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0005340576171875s
Believability | Calculation of trust value for Systems Biology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sbo took 2.6021997928619385s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2576260566711426s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020554780960083008s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010466575622558594s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-sbro took 2.540097236633301s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.25771379470825195s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0010480880737304688s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.001556396484375s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sdo took 2.5569591522216797s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.4345855712890625e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2709665298461914s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020267724990844727s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00033593177795410156s
Believability | Calculation of trust value for Sample processing and separation techniques took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-sep took 2.6054680347442627s
Availability | SPARQL endpoint availability check for Student Health Record took 4.553794860839844e-05s
Availability | VoID file availability check for Student Health Record took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2789146900177002s
Reputation | Calculation of the PageRank for Student Health Record took 0.021010875701904297s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004818439483642578s
Believability | Calculation of trust value for Student Health Record took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-shr took 2.634272336959839s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0008301734924316406s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.25585222244262695s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.02038407325744629s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.001230001449584961s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sio took 3.239464282989502s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.696846008300781e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.28343963623046875s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00020360946655273438s
Believability | Calculation of trust value for Situation-Based Access Control took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sitbac took 2.616811990737915s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.2438507080078125e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3187692165374756s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019118785858154297s
Believability | Calculation of trust value for SNOMED Clinical Terms took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-snomedct took 3.0810604095458984s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2594614028930664s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.001028299331665039s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007703304290771484s
Believability | Calculation of trust value for SNP-Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-snpo took 2.547898054122925s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.744529724121094e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.28603363037109375s
Reputation | Calculation of the PageRank for Sequence types and features took 0.021803617477416992s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005905628204345703s
Believability | Calculation of trust value for Sequence types and features took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.6127214431762695s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 5.7697296142578125e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.31624770164489746s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015876293182373047s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sopharm took 3.070474863052368s
Availability | SPARQL endpoint availability check for SoyOntology took 7.2479248046875e-05s
Availability | VoID file availability check for SoyOntology took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.2962038516998291s
Reputation | Calculation of the PageRank for SoyOntology took 0.020213603973388672s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001404285430908203s
Believability | Calculation of trust value for SoyOntology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-soy took 2.636315107345581s
Availability | SPARQL endpoint availability check for Spider Ontology took 7.62939453125e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2712976932525635s
Reputation | Calculation of the PageRank for Spider Ontology took 0.021016597747802734s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003211498260498047s
Believability | Calculation of trust value for Spider Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-spd took 2.6563022136688232s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2624518871307373s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00028395652770996094s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-spto took 2.6515164375305176s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.27898216247558594s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00045299530029296875s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sso took 2.6861023902893066s
Availability | SPARQL endpoint availability check for Software Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Software Ontology took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2572462558746338s
Reputation | Calculation of the PageRank for Software Ontology took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00042176246643066406s
Believability | Calculation of trust value for Software Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-swo took 2.627399206161499s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.27144622802734375s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002391338348388672s
Believability | Calculation of trust value for Tick gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-tads took 2.6199560165405273s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.28122448921203613s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.000888824462890625s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tao took 2.7297801971435547s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.410743713378906e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2590150833129883s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.560585021972656e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-taxrank took 2.6168975830078125s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 5.125999450683594e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.2674391269683838s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02030467987060547s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.534027099609375e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teddy took 2.621061325073242s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2672152519226074s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02019357681274414s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008032321929931641s
Believability | Calculation of trust value for Time Event Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-teo took 2.6058406829833984s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2656087875366211s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00038814544677734375s
Believability | Calculation of trust value for Mosquito gross anatomy took 3.814697265625e-06s
INFO | --- Analysis for bioportal-tgma took 2.6851842403411865s
Availability | SPARQL endpoint availability check for thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for thesaurus took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2653331756591797s
Reputation | Calculation of the PageRank for thesaurus took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.200241088867188e-05s
Believability | Calculation of trust value for thesaurus took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.6023080348968506s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.601478576660156e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2645134925842285s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.021475791931152344s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0011322498321533203s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0004279613494873047s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.6797709465026855s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.27566027641296387s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008654594421386719s
Believability | Calculation of trust value for Translational Medicine Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tmo took 2.6480934619903564s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2703723907470703s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020116806030273438s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.0001556873321533203s
Believability | Calculation of trust value for Plant Trait Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-to took 2.614400863647461s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2834970951080322s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00020241737365722656s
Believability | Calculation of trust value for TOK_Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-tok took 2.6674439907073975s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.982948303222656e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.25130605697631836s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019621849060058594s
Believability | Calculation of trust value for Teleost taxonomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-tto took 2.64040470123291s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.26323938369750977s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020122528076171875s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010089874267578125s
Believability | Calculation of trust value for Uber anatomy ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-uberon took 2.626875400543213s
Availability | SPARQL endpoint availability check for Units Ontology took 5.14984130859375e-05s
Availability | VoID file availability check for Units Ontology took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2685117721557617s
Reputation | Calculation of the PageRank for Units Ontology took 0.020921945571899414s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0010056495666503906s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002739429473876953s
Believability | Calculation of trust value for Units Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.6875858306884766s
Availability | SPARQL endpoint availability check for Units of measurement took 4.38690185546875e-05s
Availability | VoID file availability check for Units of measurement took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.26925182342529297s
Reputation | Calculation of the PageRank for Units of measurement took 0.020020008087158203s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002760887145996094s
Believability | Calculation of trust value for Units of measurement took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-uo took 2.653780698776245s
Availability | SPARQL endpoint availability check for VANDF took 4.2438507080078125e-05s
Availability | VoID file availability check for VANDF took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for VANDF took 0.26677751541137695s
Reputation | Calculation of the PageRank for VANDF took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for VANDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006842613220214844s
Believability | Calculation of trust value for VANDF took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-vandf took 2.593174457550049s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2726893424987793s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004227161407470703s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-vao took 2.6814088821411133s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.57763671875e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2806870937347412s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020199298858642578s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006434917449951172s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vhog took 2.661550521850586s
Availability | SPARQL endpoint availability check for VIVO took 4.315376281738281e-05s
Availability | VoID file availability check for VIVO took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for VIVO took 0.25902676582336426s
Reputation | Calculation of the PageRank for VIVO took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003495216369628906s
Believability | Calculation of trust value for VIVO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vivo took 2.6066396236419678s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.25049328804016113s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012385845184326172s
Believability | Calculation of trust value for Vaccine Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-vo took 2.528564929962158s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2435445785522461s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00021719932556152344s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vt took 2.4883389472961426s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.27418088912963867s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004961490631103516s
Believability | Calculation of trust value for C. elegans gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-wbbt took 2.5463783740997314s
Availability | SPARQL endpoint availability check for C. elegans development took 5.698204040527344e-05s
Availability | VoID file availability check for C. elegans development took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.26488471031188965s
Reputation | Calculation of the PageRank for C. elegans development took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.1961669921875e-05s
Believability | Calculation of trust value for C. elegans development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-wbls took 2.5166287422180176s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.458427429199219e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.285642147064209s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.463859558105469e-05s
Believability | Calculation of trust value for C. elegans phenotype took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.6097640991210938s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.363059997558594e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2830464839935303s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005967617034912109s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-who took 2.638857126235962s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.1961669921875e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2798755168914795s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006697177886962891s
Believability | Calculation of trust value for Xenopus anatomy and development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-xao took 2.6482934951782227s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.26090550422668457s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00022983551025390625s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-xco took 2.624837875366211s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.267692565917969e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.26994824409484863s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00027060508728027344s
Believability | Calculation of trust value for Yeast phenotypes took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ypo took 2.6296098232269287s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.220008850097656e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.25440287590026855s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007665157318115234s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-zfa took 2.5796966552734375s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.410743713378906e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.26029181480407715s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 6.67572021484375e-06s
INFO | --- Analysis for Bioportal_link took 3.927506446838379s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.5910768508911133s
Availability | VoID file availability check for BioSamples RDF took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2682523727416992s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020177125930786133s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 7.915496826171875e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.2159347534179688e-05s
INFO | --- Analysis for biosamples-rdf took 3.581789970397949s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 1.0323505401611328s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.27024054527282715s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020417213439941406s
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.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011277198791503906s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for bis-linked-data took 3.4454567432403564s
Availability | SPARQL endpoint availability check for Bitzi took 4.076957702636719e-05s
Availability | VoID file availability check for Bitzi took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for Bitzi took 0.25879788398742676s
Reputation | Calculation of the PageRank for Bitzi took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.123283386230469e-05s
Believability | Calculation of trust value for Bitzi took 8.106231689453125e-06s
INFO | --- Analysis for bitzi took 2.9324097633361816s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.0531158447265625e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2574148178100586s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.0279159545898438e-05s
Believability | Calculation of trust value for BizkaiSense took 7.62939453125e-06s
INFO | --- Analysis for bizkaisense took 2.919712543487549s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.124641418457031e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.25194239616394043s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0279159545898438e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.62939453125e-06s
INFO | --- Analysis for blabla-itemlist took 2.903754949569702s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.363059997558594e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.24976396560668945s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0517578125e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.62939453125e-06s
INFO | --- Analysis for blabla_itemlist took 2.9094488620758057s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007696151733398438s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2687392234802246s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.363059997558594e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for bll-thesaurus took 3.798225164413452s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 0.5045936107635498s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.26354384422302246s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.4849853515625e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 6.4373016357421875e-06s
INFO | --- Analysis for bluk-bnb took 10.25522232055664s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.3224937915802002s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006275177001953125s
Extra | Recovery of all triples for Thesaurus BNCF took 48.464412450790405s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5992038249969482s
Amount of data | Number of triples check for Thesaurus BNCF took 0.5630934238433838s
Interoperability | New terms check for Thesaurus BNCF took 1.5380845069885254s
Versatility | Languages check for Thesaurus BNCF took 7.0704872608184814s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.7262716293334961s
Security | Check HTTPS for Thesaurus BNCF took 0.08768606185913086s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1201333999633789s
Versatility | Serialization formats check for Thesaurus BNCF took 0.12619447708129883s
Availability | RDF dump link check for Thesaurus BNCF took 0.11174368858337402s
License | MR license check for Thesaurus BNCF took 0.10804128646850586s
License | HR license check for Thesaurus BNCF took 0.20059776306152344s
Amount of data | Number of property check for Thesaurus BNCF took 0.11434817314147949s
Understandability | Number of label check for Thesaurus BNCF took 0.2462754249572754s
Understandability | URI regex check for Thesaurus BNCF took 0.22112607955932617s
Understandability | Vocabs check for Thesaurus BNCF took 0.11641359329223633s
Verifiability | Authors check for Thesaurus BNCF took 0.12302446365356445s
Verifiability | Publishers check for Thesaurus BNCF took 0.1132059097290039s
Performance | Throughput check for Thesaurus BNCF took 10.898180484771729s
Amount of data | Check the number of entities for Thesaurus BNCF took 6.771087646484375e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.11387443542480469s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.11904454231262207s
Interlinking | skos check for Thesaurus BNCF took 0.1665196418762207s
Interlinking | skos check for Thesaurus BNCF took 0.14624285697937012s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.11287665367126465s
Currency | Creation date check for Thesaurus BNCF took 0.23617863655090332s
Currency | Modification date check for Thesaurus BNCF took 0.22364258766174316s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.276053190231323s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.11386418342590332s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.10014629364013672s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11428070068359375s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.596043586730957s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5156950950622559s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.9985599517822266s
Consistency | Disjoint class check for Thesaurus BNCF took 0.11620807647705078s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.777578592300415s
Consistency | Misplaced classes for Thesaurus BNCF took 7.0630433559417725s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.181994915008545s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4354143142700195s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.102226495742798s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4252805709838867s
Security | Sign check for Thesaurus BNCF took 0.1115572452545166s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.94052290916443s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.27408647537231445s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020065784454345703s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.384185791015625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 6.198883056640625e-06s
INFO | --- Analysis for bncf-ns took 188.24787425994873s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.540027379989624s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006334781646728516s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.2011725902557373s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8649570941925049s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.938642978668213s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.150319576263428s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.37421703338623s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.4791619777679443s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31223058700561523s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37696361541748047s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5202763080596924s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5408473014831543s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6439254283905029s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.36241292953491s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38904523849487305s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7966291904449463s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7482254505157471s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37185239791870117s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4507012367248535s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39262843132019043s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.395071506500244s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.557868957519531e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.25288867950439453s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4110558032989502s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3800036907196045s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3709084987640381s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4818906784057617s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7485542297363281s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.383652925491333s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.148157596588135s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.343670129776001s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.40293455123901367s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3631625175476074s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2097218036651611s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.024212360382080078s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02913379669189453s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.386293888092041s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.58855128288269s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.44725513458251953s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.650113821029663s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6894378662109375s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.564377784729004s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030661344528198242s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.43004536628723145s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39299654960632324s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.38807225227356s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7406504154205322s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.867813110351562e-06s
INFO | --- Analysis for bpr took 398.9948089122772s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.5299530029296875e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.29699254035949707s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.985664367675781e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.0067901611328125e-06s
INFO | --- Analysis for brazilian-politicians took 5.194972038269043s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.00543212890625e-05s
Availability | VoID file availability check for BrazilianCities took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.28157687187194824s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.1948089599609375e-05s
Believability | Calculation of trust value for BrazilianCities took 7.152557373046875e-06s
INFO | --- Analysis for braziliancities took 3.347090721130371s
Availability | SPARQL endpoint availability check for Bricklink took 1.4501705169677734s
Availability | VoID file availability check for Bricklink took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for Bricklink took 0.27406787872314453s
Reputation | Calculation of the PageRank for Bricklink took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.794929504394531e-05s
Believability | Calculation of trust value for Bricklink took 8.344650268554688e-06s
INFO | --- Analysis for bricklink took 9.547504186630249s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.11855983734131s
Availability | VoID file availability check for British Museum Collection took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.25919675827026367s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.910064697265625e-05s
Believability | Calculation of trust value for British Museum Collection took 7.3909759521484375e-06s
INFO | --- Analysis for british-museum-collection took 72.61709070205688s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.363059997558594e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00021028518676757812s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.25765156745910645s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02019047737121582s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.933906555175781e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 6.4373016357421875e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.9063379764556885s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.124641418457031e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2878572940826416s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02020430564880371s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.9325485229492188e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.152557373046875e-06s
INFO | --- Analysis for bsv took 3.3055591583251953s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.31915020942688s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.3015553951263428s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2636184692382812e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.3909759521484375e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 7.2112579345703125s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.100799560546875e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.2544119358062744s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.24249267578125e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 6.9141387939453125e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.909635305404663s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 5.412101745605469e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.24545645713806152s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.9802322387695312e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 7.152557373046875e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.862006187438965s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.21075773239135742s
Availability | VoID file availability check for business.data.gov.uk took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.26240992546081543s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.14984130859375e-05s
Believability | Calculation of trust value for business.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for business-data-gov-uk took 2.739151954650879s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.6253635883331299s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0007231235504150391s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.561307668685913s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.6506462097167969s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.41678476333618164s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.6971280574798584s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 30.338545322418213s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.4938526153564453s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.12020087242126465s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5743968486785889s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.4742240905761719s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2274789810180664s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.5109915733337402s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 23.93891191482544s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.273754358291626s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.8957638740539551s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.7983019351959229s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.2925536632537842s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.6498928070068359s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3668041229248047s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.436070680618286s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.486343383789062e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.914238452911377s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.9030745029449463s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.9566934108734131s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.927351713180542s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 1.3285672664642334s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 1.807041883468628s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 2.2514193058013916s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 2.2260308265686035s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 1.3003675937652588s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.030894994735717773s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 1.3073241710662842s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 1.2852680683135986s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.5859944820404053s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.0323634147644043s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 1.114276647567749s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 11.92354679107666s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.33324503898620605s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02095937728881836s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0008347034454345703s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 2.1457672119140625e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 7.3909759521484375e-06s
INFO | --- Analysis for BVMC took 144.4401571750641s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.124641418457031e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.26046299934387207s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.019780635833740234s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.0994415283203125e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 6.9141387939453125e-06s
INFO | --- Analysis for cabbage took 3.3729076385498047s
Availability | SPARQL endpoint availability check for cablegate took 1.6030361652374268s
Availability | VoID file availability check for cablegate took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for cablegate took 0.2672080993652344s
Reputation | Calculation of the PageRank for cablegate took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for cablegate took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for cablegate took 8.153915405273438e-05s
Believability | Calculation of trust value for cablegate took 7.152557373046875e-06s
INFO | --- Analysis for cablegate took 16.384454011917114s
Availability | SPARQL endpoint availability check for Calames took 4.291534423828125e-05s
Availability | VoID file availability check for Calames took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Calames took 0.26307201385498047s
Reputation | Calculation of the PageRank for Calames took 0.020186662673950195s
Interlinking | Calculation of Degree of Connection for Calames took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Calames took 3.314018249511719e-05s
Believability | Calculation of trust value for Calames took 7.3909759521484375e-06s
INFO | --- Analysis for calames took 15.621209621429443s
Availability | SPARQL endpoint availability check for CaLiGraph took 12.226808071136475s
Availability | VoID file availability check for CaLiGraph took 0.0002772808074951172s
Extra | Recovery of all triples for CaLiGraph took 31.13567590713501s
Performance | Total latancy measurement for CaLiGraph took 30.3710036277771s
Amount of data | Number of triples check for CaLiGraph took 11.891445398330688s
Versatility | Languages check for CaLiGraph took 9.997876167297363s
Interpretability | Number of blank nodes check for CaLiGraph took 1.3163342475891113s
Security | Check HTTPS for CaLiGraph took 0.13923120498657227s
Interpretability | RDF structures check for CaLiGraph took 20.561851263046265s
Versatility | Serialization formats check for CaLiGraph took 87.3659336566925s
Availability | RDF dump link check for CaLiGraph took 24.991685390472412s
License | MR license check for CaLiGraph took 5.183361768722534s
License | HR license check for CaLiGraph took 10.018437385559082s
Amount of data | Number of property check for CaLiGraph took 9.998057126998901s
Understandability | Number of label check for CaLiGraph took 16.342042207717896s
Understandability | URI regex check for CaLiGraph took 62.203030824661255s
Understandability | Vocabs check for CaLiGraph took 3.620590925216675s
Verifiability | Authors check for CaLiGraph took 0.28281354904174805s
Verifiability | Publishers check for CaLiGraph took 0.25872230529785156s
Performance | Throughput check for CaLiGraph took 46.32814598083496s
Amount of data | Check the number of entities for CaLiGraph took 0.015610456466674805s
Verifiability | Contribs. check for CaLiGraph took 0.25699472427368164s
Interlinking | sameAs chians check for CaLiGraph took 0.6315035820007324s
Interlinking | skos check for CaLiGraph took 0.39434814453125s
Interlinking | skos check for CaLiGraph took 0.2501246929168701s
Timeliness | dataset update frequency check for CaLiGraph took 0.32149505615234375s
Currency | Creation date check for CaLiGraph took 0.5436844825744629s
Currency | Modification date check for CaLiGraph took 0.5072362422943115s
Rep.Conc. | URIs length for CaLiGraph took 61.21261477470398s
Interoperability | New vocabularies check for CaLiGraph took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2694056034088135s
Accuracy | Check Functional Property for CaLiGraph took 0.32813286781311035s
Accuracy | Check Inverse Functional Property for CaLiGraph took 2.2759487628936768s
Accuracy | Check Empty annotation labels for CaLiGraph took 1.8977842330932617s
Accuracy | Check White space in annotation for CaLiGraph took 0.026571035385131836s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04990983009338379s
Consistency | Disjoint class check for CaLiGraph took 0.25601863861083984s
Consistency | Check Misplaced properties for CaLiGraph took 71.74236965179443s
Consistency | Misplaced classes for CaLiGraph took 0.5664768218994141s
Consistency | Check Ontology hijacking for CaLiGraph took 2.102689027786255s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3164935111999512s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 81.28649735450745s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.034177541732788086s
Security | Sign check for CaLiGraph took 31.02882409095764s
Availability | Check URIs Dereferenciability for CaLiGraph took 12.329185485839844s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.9658443927764893s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 7.152557373046875e-06s
INFO | --- Analysis for CaLiGraph took 1067.5979733467102s
Availability | SPARQL endpoint availability check for CaLiGraph took 9.548615455627441s
Availability | VoID file availability check for CaLiGraph took 0.0006337165832519531s
Extra | Recovery of all triples for CaLiGraph took 10.067659854888916s
Performance | Total latancy measurement for CaLiGraph took 30.20689105987549s
Amount of data | Number of triples check for CaLiGraph took 12.685965061187744s
Interoperability | New terms check for CaLiGraph took 14.027995824813843s
Versatility | Languages check for CaLiGraph took 67.46772265434265s
Interpretability | Number of blank nodes check for CaLiGraph took 0.29409337043762207s
Security | Check HTTPS for CaLiGraph took 0.12870478630065918s
Interpretability | RDF structures check for CaLiGraph took 0.27486205101013184s
Versatility | Serialization formats check for CaLiGraph took 0.2644329071044922s
Availability | RDF dump link check for CaLiGraph took 0.27419519424438477s
License | MR license check for CaLiGraph took 0.3618190288543701s
License | HR license check for CaLiGraph took 60.2906174659729s
Amount of data | Number of property check for CaLiGraph took 0.3076026439666748s
Understandability | Number of label check for CaLiGraph took 3.139000177383423s
Understandability | URI regex check for CaLiGraph took 14.786927938461304s
Understandability | Vocabs check for CaLiGraph took 38.55329704284668s
Verifiability | Authors check for CaLiGraph took 16.367673635482788s
Verifiability | Publishers check for CaLiGraph took 0.9311411380767822s
Performance | Throughput check for CaLiGraph took 160.90659761428833s
Amount of data | Check the number of entities for CaLiGraph took 3.337860107421875e-05s
Verifiability | Contribs. check for CaLiGraph took 12.279165983200073s
Interlinking | sameAs chians check for CaLiGraph took 12.1158766746521s
Interlinking | skos check for CaLiGraph took 12.881645679473877s
Interlinking | skos check for CaLiGraph took 11.33903455734253s
Timeliness | dataset update frequency check for CaLiGraph took 5.445823431015015s
Currency | Creation date check for CaLiGraph took 21.77274775505066s
Currency | Modification date check for CaLiGraph took 11.117963790893555s
Rep.Conc. | URIs length for CaLiGraph took 65.2591142654419s
Interoperability | New vocabularies check for CaLiGraph took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.24768805503845215s
Accuracy | Check Functional Property for CaLiGraph took 0.25423526763916016s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2430555820465088s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6613671779632568s
Accuracy | Check White space in annotation for CaLiGraph took 0.026668548583984375s
Consistency | Disjoint class check for CaLiGraph took 0.27534961700439453s
Consistency | Check Misplaced properties for CaLiGraph took 61.076980113983154s
Consistency | Misplaced classes for CaLiGraph took 0.5231409072875977s
Consistency | Check Ontology hijacking for CaLiGraph took 2.1255128383636475s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.6265971660614s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.00014352798461914062s
Security | Sign check for CaLiGraph took 31.50468921661377s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.864424467086792s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 8.320808410644531e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 7.3909759521484375e-06s
INFO | --- Analysis for caligraph took 3020.1437385082245s
Availability | SPARQL endpoint availability check for can-link took 4.076957702636719e-05s
Availability | VoID file availability check for can-link took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for can-link took 0.2600409984588623s
Reputation | Calculation of the PageRank for can-link took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for can-link took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for can-link took 2.8848648071289062e-05s
Believability | Calculation of trust value for can-link took 6.9141387939453125e-06s
INFO | --- Analysis for can-link took 4.885293245315552s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.0657813549041748s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.27593231201171875s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.170967102050781e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for cap-italy-rdf took 3.479942560195923s
Availability | SPARQL endpoint availability check for person took 4.3392181396484375e-05s
Availability | VoID file availability check for person took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for person took 0.6995179653167725s
Reputation | Calculation of the PageRank for person took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for person took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for person took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for person took 3.075599670410156e-05s
Believability | Calculation of trust value for person took 6.4373016357421875e-06s
INFO | --- Analysis for card took 2.8750009536743164s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.982948303222656e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.26598548889160156s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.00543212890625e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0967254638671875e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.944852113723755s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 5.221366882324219e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.24502944946289062s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020242929458618164s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.075599670410156e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 6.9141387939453125e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.9483697414398193s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 391.8879818916321s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 1.1361565589904785s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.673004150390625e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 666.8022766113281s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010514259338378906s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.720632791519165s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010824203491210938s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 8.344650268554688e-06s
INFO | --- Analysis for ce4r took 117.0531792640686s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35645437240600586s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002772808074951172s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.5980007648468018s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7423198223114014s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3192141056060791s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6938016414642334s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.1503529548645s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1401526927947998s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.33385753631591797s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15433120727539062s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1361997127532959s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26045989990234375s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3527050018310547s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15142464637756348s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3301353454589844s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.29640650749206543s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14721369743347168s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2947061061859131s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3443167209625244s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.68016767501831s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 0.00012636184692382812s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2417449951171875s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4662611484527588s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7213990688323975s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19082069396972656s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1619868278503418s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6027295589447021s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39014744758605957s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.1804654598236084s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16051626205444336s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.3230926990509033s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.3001410961151123s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6329183578491211s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.027843713760375977s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.029601335525512695s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4390981197357178s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.1784465312957764s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.1973013877868652s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.317669153213501s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4954538345336914s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03008127212524414s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.17691302299499512s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16203713417053223s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 3034.717966556549s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.533437967300415s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020142078399658203s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 7.62939453125e-06s
INFO | --- Analysis for ceo took 3162.2471516132355s
Availability | SPARQL endpoint availability check for Charging Stations took 4.2438507080078125e-05s
Availability | VoID file availability check for Charging Stations took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.7065837383270264s
Reputation | Calculation of the PageRank for Charging Stations took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.1948089599609375e-05s
Believability | Calculation of trust value for Charging Stations took 7.867813110351562e-06s
INFO | --- Analysis for charging-stations took 5.166235446929932s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.291534423828125e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.26323461532592773s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.266334533691406e-05s
Believability | Calculation of trust value for Chat Game corpus took 6.198883056640625e-06s
INFO | --- Analysis for chat-game-corpus took 13.036376237869263s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 3.981590270996094e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.29541778564453125s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.02022552490234375s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.2901763916015625e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 6.198883056640625e-06s
INFO | --- Analysis for chebi took 3.4220056533813477s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.220008850097656e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.6724355220794678s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.8650970458984375e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 8.106231689453125e-06s
INFO | --- Analysis for chem2bio2rdf took 136.24272537231445s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.7727131843566895s
Availability | VoID file availability check for ChEMBL RDF took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.26354193687438965s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020100831985473633s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 4.100799560546875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.125999450683594e-05s
Believability | Calculation of trust value for ChEMBL RDF took 6.9141387939453125e-06s
INFO | --- Analysis for chembl-rdf took 3.860055685043335s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.595196008682251s
Availability | VoID file availability check for chemdb  dataset took 0.00025963783264160156s
Extra | Recovery of all triples for chemdb  dataset took 12.227859735488892s
Performance | Total latancy measurement for chemdb  dataset took 2.466329574584961s
Amount of data | Number of triples check for chemdb  dataset took 0.5424423217773438s
Interoperability | New terms check for chemdb  dataset took 4.4840171337127686s
Versatility | Languages check for chemdb  dataset took 29.042402982711792s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5063493251800537s
Interpretability | RDF structures check for chemdb  dataset took 0.5226104259490967s
Versatility | Serialization formats check for chemdb  dataset took 1.4814493656158447s
Availability | RDF dump link check for chemdb  dataset took 0.9572176933288574s
License | MR license check for chemdb  dataset took 3.324127674102783s
License | HR license check for chemdb  dataset took 4.642543792724609s
Amount of data | Number of property check for chemdb  dataset took 0.6792616844177246s
Understandability | Number of label check for chemdb  dataset took 5.9743452072143555s
Understandability | URI regex check for chemdb  dataset took 2.957092523574829s
Understandability | Vocabs check for chemdb  dataset took 1.0135314464569092s
Verifiability | Authors check for chemdb  dataset took 1.3459227085113525s
Verifiability | Publishers check for chemdb  dataset took 1.017500638961792s
Performance | Throughput check for chemdb  dataset took 14.988192796707153s
Amount of data | Check the number of entities for chemdb  dataset took 7.2479248046875e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.7963018417358398s
Interlinking | sameAs chians check for chemdb  dataset took 2.120074987411499s
Interlinking | skos check for chemdb  dataset took 2.122161626815796s
Interlinking | skos check for chemdb  dataset took 0.48193860054016113s
Timeliness | dataset update frequency check for chemdb  dataset took 1.142993688583374s
Currency | Creation date check for chemdb  dataset took 2.4198505878448486s
Currency | Modification date check for chemdb  dataset took 1.0036721229553223s
Rep.Conc. | URIs length for chemdb  dataset took 4.1618897914886475s
Interoperability | New vocabularies check for chemdb  dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5166046619415283s
Accuracy | Check Functional Property for chemdb  dataset took 0.7997748851776123s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.789663553237915s
Accuracy | Check Empty annotation labels for chemdb  dataset took 3.395127058029175s
Accuracy | Check White space in annotation for chemdb  dataset took 0.03056788444519043s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.033820390701293945s
Consistency | Disjoint class check for chemdb  dataset took 1.8805508613586426s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2448451519012451s
Consistency | Misplaced classes for chemdb  dataset took 0.6013059616088867s
Consistency | Check Ontology hijacking for chemdb  dataset took 4.001784563064575s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3212974071502686s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.0173580646514893s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.035308122634887695s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5225458145141602s
Security | Sign check for chemdb  dataset took 2.033956527709961s
Availability | Check URIs Dereferenciability for chemdb  dataset took 3317.9895856380463s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 1.5009756088256836s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.025660037994384766s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.510185241699219e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb  dataset took 7.62939453125e-06s
INFO | --- Analysis for chemdb-basicInfo took 4417.843598604202s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 1.5335185527801514s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00025653839111328125s
Extra | Recovery of all triples for chemdb estimated properties dataset took 16.272149085998535s
Performance | Total latancy measurement for chemdb estimated properties dataset took 4.238363981246948s
Amount of data | Number of triples check for chemdb estimated properties dataset took 1.5576412677764893s
Interoperability | New terms check for chemdb estimated properties dataset took 4.186098337173462s
Versatility | Languages check for chemdb estimated properties dataset took 28.45611047744751s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5069072246551514s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.514754056930542s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.5891027450561523s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.90987229347229s
License | MR license check for chemdb estimated properties dataset took 3.5154502391815186s
License | HR license check for chemdb estimated properties dataset took 4.353169679641724s
Amount of data | Number of property check for chemdb estimated properties dataset took 1.541656732559204s
Understandability | Number of label check for chemdb estimated properties dataset took 7.911333799362183s
Understandability | URI regex check for chemdb estimated properties dataset took 2.177966594696045s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.8894476890563965s
Verifiability | Authors check for chemdb estimated properties dataset took 1.0190248489379883s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.8767392635345459s
Performance | Throughput check for chemdb estimated properties dataset took 15.513291358947754s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 6.723403930664062e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.843559741973877s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.2777481079101562s
Interlinking | skos check for chemdb estimated properties dataset took 2.3648505210876465s
Interlinking | skos check for chemdb estimated properties dataset took 0.5039787292480469s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.1120827198028564s
Currency | Creation date check for chemdb estimated properties dataset took 1.310471773147583s
Currency | Modification date check for chemdb estimated properties dataset took 2.1098082065582275s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 6.340912580490112s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 1.1839466094970703s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7827622890472412s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7614431381225586s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 3.2356936931610107s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.030074357986450195s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03388023376464844s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.8359391689300537s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2260894775390625s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6159188747406006s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 4.438037157058716s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.3419878482818604s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 2.7997403144836426s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03398251533508301s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.528907060623169s
Security | Sign check for chemdb estimated properties dataset took 2.129178524017334s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 3286.136633872986s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 1.5920119285583496s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 0.00010323524475097656s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 8.821487426757812e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 4411.037413597107s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5184216499328613s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0002498626708984375s
Extra | Recovery of all triples for chemdb phase transition dataset took 16.05832004547119s
Performance | Total latancy measurement for chemdb phase transition dataset took 3.212394952774048s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5455121994018555s
Interoperability | New terms check for chemdb phase transition dataset took 4.483292818069458s
Versatility | Languages check for chemdb phase transition dataset took 27.30566120147705s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.568751335144043s
Interpretability | RDF structures check for chemdb phase transition dataset took 1.5382108688354492s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.5883984565734863s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8305869102478027s
License | MR license check for chemdb phase transition dataset took 3.341604709625244s
License | HR license check for chemdb phase transition dataset took 4.0387513637542725s
Amount of data | Number of property check for chemdb phase transition dataset took 1.5943048000335693s
Understandability | Number of label check for chemdb phase transition dataset took 5.640796899795532s
Understandability | URI regex check for chemdb phase transition dataset took 1.861786127090454s
Understandability | Vocabs check for chemdb phase transition dataset took 0.8429546356201172s
Verifiability | Authors check for chemdb phase transition dataset took 1.8769991397857666s
Verifiability | Publishers check for chemdb phase transition dataset took 0.8039495944976807s
Performance | Throughput check for chemdb phase transition dataset took 13.926358461380005s
Amount of data | Check the number of entities for chemdb phase transition dataset took 7.152557373046875e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.7111449241638184s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.1655337810516357s
Interlinking | skos check for chemdb phase transition dataset took 2.141052722930908s
Interlinking | skos check for chemdb phase transition dataset took 0.5012104511260986s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.2133862972259521s
Currency | Creation date check for chemdb phase transition dataset took 1.3571953773498535s
Currency | Modification date check for chemdb phase transition dataset took 2.0555801391601562s
Rep.Conc. | URIs length for chemdb phase transition dataset took 4.673425912857056s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.5063214302062988s
Accuracy | Check Functional Property for chemdb phase transition dataset took 1.8393356800079346s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.8000621795654297s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 4.199653625488281s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030471324920654297s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03363847732543945s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.8062586784362793s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2533907890319824s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6011083126068115s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 5.747061491012573s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.3412067890167236s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 3.076707363128662s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.037102699279785156s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5268096923828125s
Security | Sign check for chemdb phase transition dataset took 1.998000144958496s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 3211.269331932068s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.7109355926513672s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 0.00011587142944335938s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 6.9141387939453125e-06s
INFO | --- Analysis for chemdb-phaseTransition took 4322.775185823441s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 1.2255752086639404s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.000263214111328125s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 15.767102479934692s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.512047052383423s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5456037521362305s
Interoperability | New terms check for chemdb thermochemistry dataset took 4.470918416976929s
Versatility | Languages check for chemdb thermochemistry dataset took 26.604045391082764s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5205645561218262s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5265510082244873s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.957448959350586s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.81069016456604s
License | MR license check for chemdb thermochemistry dataset took 2.808424472808838s
License | HR license check for chemdb thermochemistry dataset took 3.954200029373169s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5334088802337646s
Understandability | Number of label check for chemdb thermochemistry dataset took 6.650153398513794s
Understandability | URI regex check for chemdb thermochemistry dataset took 4.803933143615723s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.7972612380981445s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.0531928539276123s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.7635533809661865s
Performance | Throughput check for chemdb thermochemistry dataset took 15.24713945388794s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.176399230957031e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.663177490234375s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.096529483795166s
Interlinking | skos check for chemdb thermochemistry dataset took 1.891627550125122s
Interlinking | skos check for chemdb thermochemistry dataset took 0.49597597122192383s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.0717206001281738s
Currency | Creation date check for chemdb thermochemistry dataset took 1.3252005577087402s
Currency | Modification date check for chemdb thermochemistry dataset took 2.073575496673584s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.8478965759277344s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.48107409477233887s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.7785656452178955s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.7407188415527344s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 4.870109558105469s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.03035259246826172s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03338170051574707s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.8002955913543701s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2134459018707275s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6159746646881104s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 5.152891635894775s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.2868406772613525s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.9783000946044922s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.032334327697753906s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 1.2645750045776367s
Security | Sign check for chemdb thermochemistry dataset took 2.125051259994507s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 3210.5132789611816s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.7573232650756836s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 8.58306884765625e-06s
INFO | --- Analysis for chemdb-thermochemistry took 4310.875201463699s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 5.984306335449219e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.2847590446472168s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.4332275390625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 6.9141387939453125e-06s
INFO | --- Analysis for chempedia-rdf took 9.510237455368042s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.482269287109375e-05s
Availability | VoID file availability check for Chiman Maru took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.2567873001098633s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.0517578125e-05s
Believability | Calculation of trust value for Chiman Maru took 6.9141387939453125e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.4888744354248047s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.6438422203064s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.3098793029785156s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02448272705078125s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.6716461181640625e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 798.6941866874695s
Availability | SPARQL endpoint availability check for Chronicling America took 4.6253204345703125e-05s
Availability | VoID file availability check for Chronicling America took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.28575873374938965s
Reputation | Calculation of the PageRank for Chronicling America took 0.02710723876953125s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0012526512145996094s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.0001342296600341797s
Believability | Calculation of trust value for Chronicling America took 7.62939453125e-06s
INFO | --- Analysis for chronicling-america took 7.907526969909668s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.7378771305084229s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0007283687591552734s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 140.9410502910614s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.6313636302947998s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.6107399463653564s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.280014753341675s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.7116756439208984s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.6520934104919434s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.5133123397827148s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3305845260620117s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 35.105658292770386s
License | MR license check for Cultural Heritage Thesaurus took 0.32764124870300293s
License | HR license check for Cultural Heritage Thesaurus took 1.0239067077636719s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.49323606491088867s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.39232587814331055s
Understandability | URI regex check for Cultural Heritage Thesaurus took 2.129295587539673s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3395707607269287s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.3637840747833252s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.5906739234924316s
Performance | Throughput check for Cultural Heritage Thesaurus took 16.611616611480713s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.177757263183594e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.28475189208984375s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.47360825538635254s
Interlinking | skos check for Cultural Heritage Thesaurus took 1.0615949630737305s
Interlinking | skos check for Cultural Heritage Thesaurus took 1.147862195968628s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.32408928871154785s
Currency | Creation date check for Cultural Heritage Thesaurus took 2.985599994659424s
Currency | Modification date check for Cultural Heritage Thesaurus took 1.3453021049499512s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 24.083829641342163s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.2970430850982666s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3431861400604248s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2839970588684082s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 4.00186562538147s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.223646879196167s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.31471967697143555s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 0.9995956420898438s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3008122444152832s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 7.311895132064819s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.2178573608398438s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00030875205993652344s
Security | Sign check for Cultural Heritage Thesaurus took 0.3236572742462158s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 257.96333861351013s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.5562865734100342s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.3208897113800049s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0012922286987304688s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.010639667510986328s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for cht took 545.2324469089508s
Availability | SPARQL endpoint availability check for ciard-ring took 9.226799011230469e-05s
Availability | VoID file availability check for ciard-ring took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2682318687438965s
Reputation | Calculation of the PageRank for ciard-ring took 0.037943124771118164s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 5.412101745605469e-05s
Believability | Calculation of trust value for ciard-ring took 6.4373016357421875e-06s
INFO | --- Analysis for ciard-ring took 3.7827513217926025s
Availability | SPARQL endpoint availability check for Cine Figure took 4.172325134277344e-05s
Availability | VoID file availability check for Cine Figure took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.26586341857910156s
Reputation | Calculation of the PageRank for Cine Figure took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.4345855712890625e-05s
Believability | Calculation of trust value for Cine Figure took 6.198883056640625e-06s
INFO | --- Analysis for Cine_Figure took 2.5066757202148438s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.429986715316772s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.30246949195861816s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.030632019042969e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 5.9604644775390625e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 174.10108518600464s
Availability | SPARQL endpoint availability check for CIPFA took 4.744529724121094e-05s
Availability | VoID file availability check for CIPFA took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for CIPFA took 0.30156993865966797s
Reputation | Calculation of the PageRank for CIPFA took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.790855407714844e-05s
Believability | Calculation of trust value for CIPFA took 4.291534423828125e-06s
INFO | --- Analysis for cipfa took 3.2658562660217285s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 0.2783849239349365s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.28002452850341797s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00039839744567871094s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 8.344650268554688e-06s
INFO | --- Analysis for ckan took 3.046882152557373s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5049474239349365s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.27857518196105957s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.220008850097656e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for CLaSSES took 4.084182500839233s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.363059997558594e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.001115560531616211s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.29536914825439453s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.170967102050781e-05s
Believability | Calculation of trust value for Temples of the Classical World took 5.9604644775390625e-06s
INFO | --- Analysis for classical_temples took 3.5816526412963867s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 2.4478390216827393s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.29116320610046387s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.797645568847656e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 4.0531158447265625e-06s
INFO | --- Analysis for clean-energy-data-reegle took 9.422236442565918s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.57763671875e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.28281092643737793s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.915496826171875e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.049041748046875e-05s
INFO | --- Analysis for clld-afbo took 4.031161308288574s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.1484832763671875e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.26097965240478516s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.772445678710938e-05s
Believability | Calculation of trust value for CLLD-APICS took 5.4836273193359375e-06s
INFO | --- Analysis for clld-apics took 3.612168550491333s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.8160552978515625e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2759718894958496s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.910064697265625e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 8.106231689453125e-06s
INFO | --- Analysis for clld-ewave took 3.587031364440918s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.3392181396484375e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2839069366455078s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020344972610473633s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00012755393981933594s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 6.4373016357421875e-06s
INFO | --- Analysis for clld-glottolog took 3.519658327102661s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2795422077178955s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.225440979003906e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.67572021484375e-06s
INFO | --- Analysis for clld-phoible took 3.5772621631622314s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.172325134277344e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.28883957862854004s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 9.250640869140625e-05s
Believability | Calculation of trust value for CLLD-SAILS took 6.67572021484375e-06s
INFO | --- Analysis for clld-sails took 3.8265373706817627s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.482269287109375e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0012290477752685547s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2843601703643799s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.940696716308594e-05s
Believability | Calculation of trust value for CLLD-WALS took 8.106231689453125e-06s
INFO | --- Analysis for clld-wals took 3.546218156814575s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.2957277297973633s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.534027099609375e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.1682510375976562e-05s
INFO | --- Analysis for clld-wold took 3.7160322666168213s
Availability | SPARQL endpoint availability check for COD inventory took 4.124641418457031e-05s
Availability | VoID file availability check for COD inventory took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for COD inventory took 0.28665685653686523s
Reputation | Calculation of the PageRank for COD inventory took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.0994415283203125e-05s
Believability | Calculation of trust value for COD inventory took 5.7220458984375e-06s
INFO | --- Analysis for cod-inventory took 3.130309820175171s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.20559239387512207s
Availability | VoID file availability check for Cooperation Databank took 0.00021338462829589844s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.2798025608062744s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.552436828613281e-05s
Believability | Calculation of trust value for Cooperation Databank took 6.4373016357421875e-06s
INFO | --- Analysis for CoDa took 2.7126567363739014s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.1484832763671875e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.28142333030700684s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 2.86102294921875e-05s
Believability | Calculation of trust value for CODE Endpoint took 6.4373016357421875e-06s
INFO | --- Analysis for code-endpoint took 3.1750681400299072s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.4697401523590088s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.2948184013366699s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 2.9087066650390625e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 4.5299530029296875e-06s
INFO | --- Analysis for coins-openuplabs took 3.0487635135650635s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.9986276626586914s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.2672874927520752s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.153915405273438e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 5.245208740234375e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.952599048614502s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.05608320236206055s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2743706703186035s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.647804260253906e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for colinda took 2.5870532989501953s
Availability | SPARQL endpoint availability check for CN  2012 took 25.84002947807312s
Availability | VoID file availability check for CN  2012 took 0.0008940696716308594s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.28382253646850586s
Reputation | Calculation of the PageRank for CN  2012 took 0.020727157592773438s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.910064697265625e-05s
Believability | Calculation of trust value for CN  2012 took 6.67572021484375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 127.85464096069336s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 3.9577484130859375e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.29059433937072754s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.02015066146850586s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 2.6941299438476562e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 1.2636184692382812e-05s
INFO | --- Analysis for comments-on-literature-in-literature took 3.1604418754577637s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 5.984306335449219e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2782001495361328s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.24249267578125e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 8.106231689453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 3.1715214252471924s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.1484832763671875e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.278759241104126s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.218650817871094e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 7.62939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 4.06303071975708s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 6.556510925292969e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.28995299339294434s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.9802322387695312e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 7.62939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 4.568941354751587s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.100799560546875e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.3002181053161621s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.3909759521484375e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 4.251765966415405s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.45561933517456055s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.4435129165649414s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for CompHistSem took 4.9083640575408936s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 90.19854474067688s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0007953643798828125s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.31787753105163574s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.00543212890625e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 6.9141387939453125e-06s
INFO | --- Analysis for comsode-d3-2 took 141.45382809638977s
Availability | SPARQL endpoint availability check for ConceptNet took 4.0531158447265625e-05s
Availability | VoID file availability check for ConceptNet took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.3002815246582031s
Reputation | Calculation of the PageRank for ConceptNet took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.9802322387695312e-05s
Believability | Calculation of trust value for ConceptNet took 5.7220458984375e-06s
INFO | --- Analysis for conceptnet took 3.112191677093506s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.839897155761719e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.26053595542907715s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020500659942626953s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.225440979003906e-05s
Believability | Calculation of trust value for 2011 US Congress People took 4.0531158447265625e-06s
INFO | --- Analysis for congresspeople took 3.0026988983154297s
Availability | SPARQL endpoint availability check for MIMO took 0.28751349449157715s
Availability | VoID file availability check for MIMO took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for MIMO took 0.2895517349243164s
Reputation | Calculation of the PageRank for MIMO took 0.02242898941040039s
Interlinking | Calculation of Degree of Connection for MIMO took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.1205673217773438e-05s
Believability | Calculation of trust value for MIMO took 1.0967254638671875e-05s
INFO | --- Analysis for CONNECTED took 3.7058308124542236s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.26949119567871094s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.886222839355469e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 3.0985991954803467s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.124641418457031e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2786374092102051s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.123283386230469e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 8.344650268554688e-06s
INFO | --- Analysis for copac-library-catalogue took 3.1405389308929443s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.363059997558594e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.30396056175231934s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.021010160446166992s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.457069396972656e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.67572021484375e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.8879425525665283s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.220008850097656e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.28749823570251465s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.128715515136719e-05s
Believability | Calculation of trust value for CopyrightTermBank took 8.344650268554688e-06s
INFO | --- Analysis for copyrighttermbank took 34.135313987731934s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.3302154541015625s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.27974748611450195s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.02013373374938965s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.743171691894531e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 6.9141387939453125e-06s
INFO | --- Analysis for core took 7.214064836502075s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 392.82590651512146s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.35749244689941406s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.315376281738281e-05s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Corine_linked_dataset took 667.8009550571442s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.100799560546875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.28455185890197754s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 2.7179718017578125e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.152557373046875e-06s
INFO | --- Analysis for corn took 3.756458282470703s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.220008850097656e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2890627384185791s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020935773849487305s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0009629726409912109s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.4332275390625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 7.152557373046875e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 3.0758779048919678s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.410743713378906e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.3009328842163086s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.647804260253906e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 7.3909759521484375e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 3.058128833770752s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 5.078315734863281e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.2911221981048584s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 7.581710815429688e-05s
Believability | Calculation of trust value for Cornetto1.2 took 6.9141387939453125e-06s
INFO | --- Analysis for cornetto took 13.784735441207886s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.2889857292175293s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0004315376281738281s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 88.43770742416382s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6858007907867432s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 143.32923793792725s
Interoperability | New terms check for Corporate Body Named Authority List  took 114.3185031414032s
Versatility | Languages check for Corporate Body Named Authority List  took 300.121702671051s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 1.6507129669189453s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.35476112365722656s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.6348485946655273s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 4.215521335601807s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.25194478034973145s
License | MR license check for Corporate Body Named Authority List  took 0.36269330978393555s
License | HR license check for Corporate Body Named Authority List  took 300.05190682411194s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.18817973136901855s
Understandability | Number of label check for Corporate Body Named Authority List  took 6.7777018547058105s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.3705310821533203s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.11906957626342773s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.17289447784423828s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.25646305084228516s
Performance | Throughput check for Corporate Body Named Authority List  took 10.503575801849365s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 8.130073547363281e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.16884088516235352s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 11.602889060974121s
Interlinking | skos check for Corporate Body Named Authority List  took 0.4584932327270508s
Interlinking | skos check for Corporate Body Named Authority List  took 0.43776679039001465s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.27158474922180176s
Currency | Creation date check for Corporate Body Named Authority List  took 0.31388044357299805s
Currency | Modification date check for Corporate Body Named Authority List  took 0.21208977699279785s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 516.7399551868439s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.15636777877807617s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.2195603847503662s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.09479665756225586s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 27.998727798461914s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.150763750076294s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6330058574676514s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.15746593475341797s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.44727325439453s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.51645565032959s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 39.110368490219116s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.5992851257324219s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.52256202697754s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.01291561126709s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.5481500625610352s
Security | Sign check for Corporate Body Named Authority List  took 0.1476726531982422s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 4.279407024383545s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.7939050197601318s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02106475830078125s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.6689300537109375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 6.4373016357421875e-06s
INFO | --- Analysis for corporate-body took 15043.640410423279s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.561692476272583s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.2784452438354492s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 7.62939453125e-06s
INFO | --- Analysis for CorpusFibonacci took 5.408946514129639s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.744529724121094e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.260678768157959s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for corscheck took 3.4012701511383057s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.12526416778564453s
Availability | VoID file availability check for Country Name Authority List took 0.0006706714630126953s
Extra | Recovery of all triples for Country Name Authority List took 114.40561389923096s
Performance | Total latancy measurement for Country Name Authority List took 0.6026473045349121s
Amount of data | Number of triples check for Country Name Authority List took 93.68889617919922s
Interoperability | New terms check for Country Name Authority List took 107.53059363365173s
Versatility | Languages check for Country Name Authority List took 300.0772988796234s
Interpretability | Number of blank nodes check for Country Name Authority List took 1.3152339458465576s
Security | Check HTTPS for Country Name Authority List took 0.21111297607421875s
Interpretability | RDF structures check for Country Name Authority List took 0.6375563144683838s
Versatility | Serialization formats check for Country Name Authority List took 3.5056405067443848s
Availability | RDF dump link check for Country Name Authority List took 0.3874166011810303s
License | MR license check for Country Name Authority List took 0.3660876750946045s
License | HR license check for Country Name Authority List took 300.07693791389465s
Amount of data | Number of property check for Country Name Authority List took 0.18324017524719238s
Understandability | Number of label check for Country Name Authority List took 6.401298999786377s
Understandability | URI regex check for Country Name Authority List took 0.21943974494934082s
Understandability | Vocabs check for Country Name Authority List took 0.11598038673400879s
Verifiability | Authors check for Country Name Authority List took 0.26280784606933594s
Verifiability | Publishers check for Country Name Authority List took 0.21507716178894043s
Performance | Throughput check for Country Name Authority List took 17.374638319015503s
Amount of data | Check the number of entities for Country Name Authority List took 7.2479248046875e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.19359970092773438s
Interlinking | sameAs chians check for Country Name Authority List took 11.860984563827515s
Interlinking | skos check for Country Name Authority List took 0.26606297492980957s
Interlinking | skos check for Country Name Authority List took 0.5190515518188477s
Timeliness | dataset update frequency check for Country Name Authority List took 0.21298694610595703s
Currency | Creation date check for Country Name Authority List took 0.5106472969055176s
Currency | Modification date check for Country Name Authority List took 0.26312923431396484s
Rep.Conc. | URIs length for Country Name Authority List took 642.921017408371s
Interoperability | New vocabularies check for Country Name Authority List took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.17381668090820312s
Accuracy | Check Functional Property for Country Name Authority List took 0.15787029266357422s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.21289372444152832s
Accuracy | Check Empty annotation labels for Country Name Authority List took 28.772711992263794s
Accuracy | Check White space in annotation for Country Name Authority List took 3.1397764682769775s
Accuracy | Check Datatype consistency for Country Name Authority List took 8.153425931930542s
Consistency | Disjoint class check for Country Name Authority List took 0.1396317481994629s
Consistency | Check Misplaced properties for Country Name Authority List took 300.3736970424652s
Consistency | Misplaced classes for Country Name Authority List took 8.728118419647217s
Consistency | Check Ontology hijacking for Country Name Authority List took 26.34655499458313s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.5541930198669434s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.53324007987976s
Conciseness | Check Extensional conciseness for Country Name Authority List took 9.30601716041565s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4233968257904053s
Security | Sign check for Country Name Authority List took 0.147385835647583s
Availability | Check URIs Dereferenciability for Country Name Authority List took 4.537415266036987s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.987128496170044s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.22745990753173828s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0008759498596191406s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.866455078125e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 5.4836273193359375e-06s
Believability | Calculation of trust value for Country Name Authority List took 7.867813110351562e-06s
INFO | --- Analysis for country-authority-list took 15312.917789936066s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.11707067489624023s
Availability | VoID file availability check for Courts thesaurus took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.27686333656311035s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.890296936035156e-05s
Believability | Calculation of trust value for Courts thesaurus took 5.9604644775390625e-06s
INFO | --- Analysis for courts-thesaurus took 3.481757402420044s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.638880729675293s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.7201278209686279s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.748603820800781e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 7.152557373046875e-06s
INFO | --- Analysis for Covid-on-the-Web took 7.620072603225708s
Availability | SPARQL endpoint availability check for CPA 2008 took 26.29798197746277s
Availability | VoID file availability check for CPA 2008 took 0.0008006095886230469s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.27252817153930664s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.553794860839844e-05s
Believability | Calculation of trust value for CPA 2008 took 4.76837158203125e-06s
INFO | --- Analysis for cpa-2008 took 128.1746690273285s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.49625730514526367s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005657672882080078s
Extra | Recovery of all triples for Cooperative Patent Classification took 45.07068204879761s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.9232120513916016s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.17509531974792s
Versatility | Languages check for Cooperative Patent Classification took 120.14558243751526s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.24916195869446s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.24161362648010254s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.26732897758483887s
Availability | RDF dump link check for Cooperative Patent Classification took 0.24147319793701172s
License | MR license check for Cooperative Patent Classification took 0.22747159004211426s
License | HR license check for Cooperative Patent Classification took 90.18930292129517s
Amount of data | Number of property check for Cooperative Patent Classification took 0.21022963523864746s
Understandability | Number of label check for Cooperative Patent Classification took 90.19819188117981s
Understandability | URI regex check for Cooperative Patent Classification took 0.5342552661895752s
Understandability | Vocabs check for Cooperative Patent Classification took 0.20099329948425293s
Verifiability | Authors check for Cooperative Patent Classification took 0.2592935562133789s
Verifiability | Publishers check for Cooperative Patent Classification took 0.2082359790802002s
Performance | Throughput check for Cooperative Patent Classification took 11.088448286056519s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.295608520507812e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.3923683166503906s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.15957856178283691s
Interlinking | skos check for Cooperative Patent Classification took 0.18964052200317383s
Interlinking | skos check for Cooperative Patent Classification took 0.17486953735351562s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.16592764854431152s
Currency | Creation date check for Cooperative Patent Classification took 0.35947322845458984s
Currency | Modification date check for Cooperative Patent Classification took 0.43895602226257324s
Rep.Conc. | URIs length for Cooperative Patent Classification took 153.20880675315857s
Interoperability | New vocabularies check for Cooperative Patent Classification took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.18454527854919434s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 17.873616218566895s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9868834018707275s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.904654502868652s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.20288610458374023s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.36502265930176s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 20.97043251991272s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.6064374446868896s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.5075044631958s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.7971880435943604s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.6231808662414551s
Security | Sign check for Cooperative Patent Classification took 0.30816197395324707s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.9275519847869873s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.4899473190307617s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.021404266357421875s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 2.1457672119140625e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 7.152557373046875e-06s
INFO | --- Analysis for CPC took 1311.3934009075165s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.14435338973999s
Availability | VoID file availability check for CPC 2008 took 0.0008170604705810547s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.7209982872009277s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.4809112548828125e-05s
Believability | Calculation of trust value for CPC 2008 took 5.0067901611328125e-06s
INFO | --- Analysis for cpc-2008 took 126.98324990272522s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.45544672012329s
Availability | VoID file availability check for CPV  2003 took 0.0008478164672851562s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3993861675262451s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02090597152709961s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.220008850097656e-05s
Believability | Calculation of trust value for CPV  2003 took 5.4836273193359375e-06s
INFO | --- Analysis for cpv-2003 took 115.72906947135925s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.364789485931396s
Availability | VoID file availability check for CPV 2008 took 0.0008280277252197266s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.2878875732421875s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.078315734863281e-05s
Believability | Calculation of trust value for CPV 2008 took 5.0067901611328125e-06s
INFO | --- Analysis for cpv-2008 took 126.24449253082275s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.17255187034607s
Availability | VoID file availability check for crowdsourcing-fb took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.2712438106536865s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.6253204345703125e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 6.4373016357421875e-06s
INFO | --- Analysis for crowdsourcing-fb took 536.1073853969574s
Availability | SPARQL endpoint availability check for CRTM took 4.839897155761719e-05s
Availability | VoID file availability check for CRTM took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for CRTM took 0.690542459487915s
Reputation | Calculation of the PageRank for CRTM took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for CRTM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.4809112548828125e-05s
Believability | Calculation of trust value for CRTM took 7.3909759521484375e-06s
INFO | --- Analysis for crtm took 6.393355131149292s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.124641418457031e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.27916383743286133s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020234346389770508s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 2.86102294921875e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 7.152557373046875e-06s
INFO | --- Analysis for crystal-eye took 3.441344738006592s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.876303195953369s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.3288893699645996s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.696846008300781e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 4.76837158203125e-06s
INFO | --- Analysis for ctic-public-dataset took 44.12842917442322s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.220008850097656e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.25943922996520996s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.0279159545898438e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 6.9141387939453125e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.3535919189453125s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.6521079540252686s
Availability | VoID file availability check for CulturaLinkedData took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.2656111717224121s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.266334533691406e-05s
Believability | Calculation of trust value for CulturaLinkedData took 7.62939453125e-06s
INFO | --- Analysis for culturalinkeddata took 3.695952892303467s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.23020458221435547s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.27769041061401367s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 4.0531158447265625e-06s
INFO | --- Analysis for cz-ares-or took 2.9195191860198975s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11229753494262695s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.25934433937072754s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.552436828613281e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ares-rzp took 3.2562217712402344s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11289048194885254s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.28398656845092773s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007174015045166016s
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 4.0531158447265625e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.9123549461364746s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.11804819107055664s
Availability | VoID file availability check for Integrated pollution registry took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.26625776290893555s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.719329833984375e-05s
Believability | Calculation of trust value for Integrated pollution registry took 4.0531158447265625e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.8887457847595215s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10532402992248535s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2544243335723877s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007174015045166016s
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.7220458984375e-06s
INFO | --- Analysis for cz-contracts took 2.779839515686035s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 6.532669067382812e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.2631974220275879s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020615577697753906s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.0994415283203125e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-courts took 2.973569393157959s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10599708557128906s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2579665184020996s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.457069396972656e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-bans took 5.004461765289307s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10246515274047852s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.25444865226745605s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.504753112792969e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.8011956214904785s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11378335952758789s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.24706220626831055s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.4332275390625e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 4.291534423828125e-06s
INFO | --- Analysis for cz-ctia-focus took 2.6865246295928955s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.1163480281829834s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2716338634490967s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 5.316734313964844e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.843632698059082s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.13018202781677246s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.27962684631347656s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.647804260253906e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 8.58306884765625e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.551978826522827s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 10.18857455253601s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0011174678802490234s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.2533435821533203s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.790855407714844e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 4.5299530029296875e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 22.933485746383667s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 10.16884994506836s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.26923608779907227s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.457069396972656e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 5.0067901611328125e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 22.957067489624023s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.8638269901275635s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2720916271209717s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.00543212890625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.8967978954315186s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.4548192024230957s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0009891986846923828s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.26489925384521484s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020289182662963867s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.381664276123047s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.41027164459228516s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.26024699211120605s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020188093185424805s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.792213439941406e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.345968008041382s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.39619874954223633s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2947871685028076s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.337054491043091s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.4663369655609131s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2692375183105469s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020252466201782227s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.743171691894531e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.4253177642822266s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3939788341522217s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0008325576782226562s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2662057876586914s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020244836807250977s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.337860107421875e-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.089313507080078s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.38303470611572266s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.27457118034362793s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02024078369140625s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.2806692123413086s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.4200904369354248s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2814652919769287s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020218849182128906s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.719329833984375e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 4.291534423828125e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.401153564453125s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.37990498542785645s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2632124423980713s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.719329833984375e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.247260093688965s
Availability | SPARQL endpoint availability check for ATC groups took 0.11935615539550781s
Availability | VoID file availability check for ATC groups took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for ATC groups took 0.25126075744628906s
Reputation | Calculation of the PageRank for ATC groups took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.747245788574219e-05s
Believability | Calculation of trust value for ATC groups took 5.9604644775390625e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.7788891792297363s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10505247116088867s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.24218440055847168s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.02016925811767578s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.4332275390625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.245208740234375e-06s
INFO | --- Analysis for cz-fulfillments took 2.6575889587402344s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.04375743865966797s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.25983476638793945s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.02004861831665039s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.5299530029296875e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 9.298324584960938e-06s
INFO | --- Analysis for cz-ic took 3.1209354400634766s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.13564348220825195s
Availability | VoID file availability check for List of Czech data boxes took 0.0005681514739990234s
Extra | Recovery of all triples for List of Czech data boxes took 245.77920269966125s
Performance | Total latancy measurement for List of Czech data boxes took 0.6103215217590332s
Amount of data | Number of triples check for List of Czech data boxes took 62.008363008499146s
Interoperability | New terms check for List of Czech data boxes took 17.333152055740356s
Versatility | Languages check for List of Czech data boxes took 300.194721698761s
Interpretability | Number of blank nodes check for List of Czech data boxes took 6.0753173828125s
Interpretability | RDF structures check for List of Czech data boxes took 0.1971266269683838s
Versatility | Serialization formats check for List of Czech data boxes took 0.5985450744628906s
Availability | RDF dump link check for List of Czech data boxes took 42.82546019554138s
License | MR license check for List of Czech data boxes took 0.3889892101287842s
License | HR license check for List of Czech data boxes took 129.69495749473572s
Amount of data | Number of property check for List of Czech data boxes took 0.1499795913696289s
Understandability | Number of label check for List of Czech data boxes took 2.585832357406616s
Understandability | URI regex check for List of Czech data boxes took 0.38522791862487793s
Understandability | Vocabs check for List of Czech data boxes took 0.1342310905456543s
Verifiability | Authors check for List of Czech data boxes took 0.2782158851623535s
Verifiability | Publishers check for List of Czech data boxes took 0.22037792205810547s
Performance | Throughput check for List of Czech data boxes took 10.448922157287598s
Amount of data | Check the number of entities for List of Czech data boxes took 3.125279188156128s
Verifiability | Contribs. check for List of Czech data boxes took 3.361647605895996s
Interlinking | sameAs chians check for List of Czech data boxes took 1.7450041770935059s
Interlinking | skos check for List of Czech data boxes took 0.3623697757720947s
Interlinking | skos check for List of Czech data boxes took 0.10098791122436523s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.730475664138794s
Currency | Creation date check for List of Czech data boxes took 1.0559818744659424s
Currency | Modification date check for List of Czech data boxes took 0.14844632148742676s
Rep.Conc. | URIs length for List of Czech data boxes took 189.4892966747284s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.45132970809936523s
Accuracy | Check Functional Property for List of Czech data boxes took 0.14861083030700684s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.14315080642700195s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 61.343419551849365s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.09014630317688s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.599060535430908s
Consistency | Disjoint class check for List of Czech data boxes took 0.11217284202575684s
Consistency | Check Misplaced properties for List of Czech data boxes took 89.22362995147705s
Consistency | Misplaced classes for List of Czech data boxes took 8.003949880599976s
Consistency | Check Ontology hijacking for List of Czech data boxes took 84.6977014541626s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.4285454750061035s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 82.53441095352173s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.6502137184143066s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.6656501293182373s
Security | Sign check for List of Czech data boxes took 0.18409228324890137s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 12.130624771118164s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 1.1251404285430908s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02160167694091797s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 6.127357482910156e-05s
Believability | Calculation of trust value for List of Czech data boxes took 1.0013580322265625e-05s
INFO | --- Analysis for cz-list-of-databoxes took 2123.458220720291s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12878108024597168s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005307197570800781s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 249.33784556388855s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.57647705078125s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 35.71992325782776s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.662709712982178s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.13281416893005s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.501906156539917s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1117396354675293s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5881173610687256s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 39.98130774497986s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1635727882385254s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 145.2163667678833s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.22006797790527344s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.1907708644866943s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2482469081878662s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1308910846710205s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.20080828666687012s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1680762767791748s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.411416053771973s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.2603442668914795s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6135222911834717s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.9955337047576904s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2498924732208252s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1676347255706787s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6739635467529297s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7235751152038574s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.224076509475708s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 194.50143122673035s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.44422483444213867s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10901594161987305s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10884904861450195s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 74.42321968078613s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.1988449096679688s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.670213222503662s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11548614501953125s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 99.60788154602051s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 12.385421752929688s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 79.58163857460022s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4498188495635986s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 94.71265649795532s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.669281482696533s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8209707736968994s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1009833812713623s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 510.72962641716003s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.412717580795288s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020864486694335938s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.528594970703125e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.245208740234375e-06s
INFO | --- Analysis for cz-nace took 2308.303205013275s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5490095615386963s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005404949188232422s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 180.21437311172485s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.7804415225982666s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.31352782249450684s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5452690124511719s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 41.792171239852905s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.47502994537353516s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.19746661186218262s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.730368137359619s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3049733638763428s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3379392623901367s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5552675724029541s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17664432525634766s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4452977180480957s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3467721939086914s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17873334884643555s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17410016059875488s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2778205871582031s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.705482244491577s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.341934204101562e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15947318077087402s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20720434188842773s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.29813313484191895s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16227483749389648s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7698817253112793s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.37753772735595703s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.32284045219421387s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 58.04501748085022s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16067790985107422s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17972493171691895s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1761178970336914s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 40.619802474975586s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.4140028953552246s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.8367185592651367s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1887369155883789s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.031029462814331s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.395009517669678s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 97.22809290885925s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8243966102600098s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.2973716259002686s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.5827183723449707s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2301480770111084s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.45790576934814453s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1004.2352106571198s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.1621367931365967s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.123283386230469e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.76837158203125e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.4836273193359375e-06s
INFO | --- Analysis for cz-nkod took 69086.29364418983s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.21326494216918945s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.24544382095336914s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.5762786865234375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 4.5299530029296875e-06s
INFO | --- Analysis for cz-orders took 2.785550832748413s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.20453715324401855s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0004563331604003906s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 244.29034614562988s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5414998531341553s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 63.903563261032104s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 16.740896224975586s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1211543083191s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 2.767796516418457s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.18865656852722168s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.5797445774078369s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 40.641589879989624s
License | MR license check for Institutions of public power of the Czech Republic took 0.32625317573547363s
License | HR license check for Institutions of public power of the Czech Republic took 140.77579545974731s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.22305798530578613s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 3.2642104625701904s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.47141551971435547s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.1423945426940918s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.268481969833374s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.2640719413757324s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.758806705474854s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.2088849544525146s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.23687958717346191s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.8603770732879639s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.18165802955627441s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.0970609188079834s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.25457048416137695s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.5412642955780029s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.13936090469360352s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 189.92163491249084s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.5225348472595215s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.1349315643310547s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.1644456386566162s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 62.51952624320984s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.1142170429229736s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.637578010559082s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.11661005020141602s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 91.38883948326111s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.936270713806152s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 80.10590076446533s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.3466007709503174s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 81.47285604476929s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6354382038116455s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.5686206817626953s
Security | Sign check for Institutions of public power of the Czech Republic took 0.17219805717468262s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 11.727013111114502s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.5565652847290039s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.027513742446899414s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 3.170967102050781e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0015439987182617188s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 9.465217590332031e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-ovm took 2100.005038499832s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10464978218078613s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.3018777370452881s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.361701965332031e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ovm-agendas took 4.160888195037842s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 20.15367341041565s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.717677116394043s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0008616447448730469s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.961822509765625e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ruian took 115.19949984550476s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7543060779571533s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.261707067489624s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020111799240112305s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 6.818771362304688e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 5.573787450790405s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.44971704483032227s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.2679438591003418s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020267009735107422s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.457069396972656e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.5175564289093018s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.5185227394104004s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.25894618034362793s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.147125244140625e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 4.76837158203125e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.525333881378174s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10808110237121582s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.2751448154449463s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.314018249511719e-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 2.8220601081848145s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10786771774291992s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.25004148483276367s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.0517578125e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.7120988368988037s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.10640168190002441s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2732245922088623s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.457069396972656e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.720428466796875s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.11069107055664062s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005412101745605469s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 240.47409105300903s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5892834663391113s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 28.60237741470337s
Interoperability | New terms check for Summary types of Czech institutions of public power took 17.59599542617798s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.15715074539185s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 4.274880409240723s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.11745929718017578s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 1.3805668354034424s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 40.531675815582275s
License | MR license check for Summary types of Czech institutions of public power took 0.15450501441955566s
License | HR license check for Summary types of Czech institutions of public power took 175.86605715751648s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.15171456336975098s
Understandability | Number of label check for Summary types of Czech institutions of public power took 2.794193744659424s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.27363038063049316s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.15534043312072754s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.3115391731262207s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.20624732971191406s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.5687415599823s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.175900459289551s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.3091268539428711s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.46069836616516113s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.14546608924865723s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1129145622253418s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.1281883716583252s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.38925862312316895s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.12283802032470703s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 188.5476291179657s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.46231579780578613s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.16663217544555664s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.11007046699523926s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 74.57886290550232s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.1133198738098145s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.703401803970337s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.1291801929473877s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 93.03830814361572s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 8.356204986572266s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 69.62480878829956s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.2698922157287598s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 81.15183353424072s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.6374704837799072s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.5606594085693359s
Security | Sign check for Summary types of Czech institutions of public power took 0.11161589622497559s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 532.6871347427368s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.1402125358581543s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.025670528411865234s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 5.125999450683594e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.245208740234375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2334.0265650749207s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.09899473190307617s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2946960926055908s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020252466201782227s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.2901763916015625e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 4.183352470397949s
Availability | SPARQL endpoint availability check for State funding providers took 0.11246824264526367s
Availability | VoID file availability check for State funding providers took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for State funding providers took 0.7081027030944824s
Reputation | Calculation of the PageRank for State funding providers took 0.02001643180847168s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.695487976074219e-05s
Believability | Calculation of trust value for State funding providers took 8.106231689453125e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.260970115661621s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10361576080322266s
Availability | VoID file availability check for Organizations active in R&D took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.28945231437683105s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020087003707885742s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.695487976074219e-05s
Believability | Calculation of trust value for Organizations active in R&D took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.9100489616394043s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.1147463321685791s
Availability | VoID file availability check for R&D Programmes took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2751181125640869s
Reputation | Calculation of the PageRank for R&D Programmes took 0.02005791664123535s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.647804260253906e-05s
Believability | Calculation of trust value for R&D Programmes took 9.059906005859375e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.7737584114074707s
Availability | SPARQL endpoint availability check for R&D Projects took 0.10876679420471191s
Availability | VoID file availability check for R&D Projects took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2625150680541992s
Reputation | Calculation of the PageRank for R&D Projects took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.363059997558594e-05s
Believability | Calculation of trust value for R&D Projects took 4.291534423828125e-06s
INFO | --- Analysis for cz-vavai-projects took 3.202315092086792s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11110806465148926s
Availability | VoID file availability check for Institutional research plans took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.2670159339904785s
Reputation | Calculation of the PageRank for Institutional research plans took 0.02031087875366211s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.8623809814453125e-05s
Believability | Calculation of trust value for Institutional research plans took 8.106231689453125e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.7899270057678223s
Availability | SPARQL endpoint availability check for Results of R&D took 0.10540962219238281s
Availability | VoID file availability check for Results of R&D took 0.0007836818695068359s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.25801825523376465s
Reputation | Calculation of the PageRank for Results of R&D took 0.020319223403930664s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.790855407714844e-05s
Believability | Calculation of trust value for Results of R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-results took 2.800813674926758s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.1054069995880127s
Availability | VoID file availability check for Tenders in R&D took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.263385534286499s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.458427429199219e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.77592134475708s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.315376281738281e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.27130770683288574s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020180940628051758s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.170967102050781e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 7.152557373046875e-06s
INFO | --- Analysis for czech_addresses took 4.830597162246704s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5327408313751221s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2542610168457031s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 7.62939453125e-06s
INFO | --- Analysis for DanteLatinLoanwords took 3.9410555362701416s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3730180263519287s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006544589996337891s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 151.5688021183014s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.020676851272583s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 9.445366382598877s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.010969638824463s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.31167030334473s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.32399415969848633s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.11287593841552734s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 1.1045093536376953s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.35140490531921387s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.32456398010253906s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.500291109085083s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 72.35549187660217s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.23522710800170898s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 2.9649250507354736s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.7514123916625977s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2871286869049072s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.27349257469177246s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2380540370941162s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.138909339904785s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.081031799316406e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.23976421356201172s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.4701831340789795s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.9312915802001953s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.0715620517730713s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2294318675994873s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 3.1933064460754395s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.9726743698120117s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 79.27713108062744s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2177879810333252s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.5398423671722412s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.36571717262268066s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 41.72081017494202s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.157111644744873s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6235904693603516s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.29592227935791016s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 12.736657857894897s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.666663408279419s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 47.90802574157715s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5532400608062744s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 13.85033369064331s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8401660919189453s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.24849677085876465s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.24521112442016602s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 8.73754096031189s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.8724403381347656s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.023595571517944336s
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.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014591217041015625s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.3113021850585938e-05s
INFO | --- Analysis for data-bnf-fr took 782.7747597694397s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.11607527732849121s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005712509155273438s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.6647253036499023s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.30452632904052734s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 4.4397008419036865s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.156442642211914s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.08081388473510742s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.5929341316223145s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.039880990982055664s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.09841704368591309s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.09378790855407715s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.08137845993041992s
License | MR license check for Open Data from the Italian National Research Council took 0.10408663749694824s
License | HR license check for Open Data from the Italian National Research Council took 11.651581764221191s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.08822894096374512s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.841764450073242s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.163909912109375s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.1104423999786377s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.08522725105285645s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.08054399490356445s
Performance | Throughput check for Open Data from the Italian National Research Council took 10.202819347381592s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 7.081031799316406e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.08224678039550781s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.08277177810668945s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.0817422866821289s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.05272507667541504s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.0861821174621582s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.17644739151000977s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.1775517463684082s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 11.802274942398071s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.08089971542358398s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.08230137825012207s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.07953882217407227s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.3897721767425537s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.0324854850769043s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.027881383895874023s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.0967864990234375s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 9.981819152832031s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.18216753005981445s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.5418915748596191s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.2219758033752441s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 11.461677074432373s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03194141387939453s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.10085248947143555s
Security | Sign check for Open Data from the Italian National Research Council took 0.08655548095703125s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 606.7761781215668s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.8170058727264404s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 8.20159912109375e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.4836273193359375e-06s
INFO | --- Analysis for data-cnr-it took 706.1112101078033s
Availability | SPARQL endpoint availability check for Data.gov took 1.7808985710144043s
Availability | VoID file availability check for Data.gov took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Data.gov took 0.2591066360473633s
Reputation | Calculation of the PageRank for Data.gov took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.552436828613281e-05s
Believability | Calculation of trust value for Data.gov took 4.5299530029296875e-06s
INFO | --- Analysis for data-gov took 20.010584354400635s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.08208179473876953s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.26160216331481934s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.651878356933594e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 7.3909759521484375e-06s
INFO | --- Analysis for data-gov-ie took 4.0905821323394775s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.220008850097656e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2613203525543213s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020122766494750977s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 6.699562072753906e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 5.245208740234375e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 3.300973892211914s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.758440732955933s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.8350834846496582s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.270408630371094e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for data-hnm-hu took 167.16332030296326s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.14315485954284668s
Availability | VoID file availability check for Climb Dataincubator took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2689015865325928s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.772445678710938e-05s
Believability | Calculation of trust value for Climb Dataincubator took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-climb took 3.0684750080108643s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.26706790924072266s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 8.988380432128906e-05s
Believability | Calculation of trust value for Discogs in RDF took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-discogs took 7.301909446716309s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05932903289794922s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0008826255798339844s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.28064894676208496s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.14984130859375e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 4.291534423828125e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.680347919464111s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.0753018856048584s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.27347874641418457s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.02062082290649414s
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.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 0.000102996826171875s
Believability | Calculation of trust value for Moseley Folk Festival Data took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-moseley took 7.801363945007324s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05390572547912598s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.25534629821777344s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.463859558105469e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.455540895462036s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 2.6229918003082275s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.275005578994751s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02017807960510254s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.344650268554688e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 4.76837158203125e-06s
INFO | --- Analysis for data-incubator-nasa took 12.70381760597229s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.060441017150878906s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2697007656097412s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 6.985664367675781e-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.4384710788726807s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06377601623535156s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.24286603927612305s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02030205726623535s
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.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 8.678436279296875e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.198883056640625e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.081851005554199s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.05308842658996582s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00034999847412109375s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.26764512062072754s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.225440979003906e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.467703104019165s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.6721546649932861s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006372928619384766s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 69.45572113990784s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.292085886001587s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 0.2738168239593506s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.4683477878570557s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 8.162904024124146s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 0.2793464660644531s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.13456463813781738s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.3081328868865967s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.31847596168518066s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.2907431125640869s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.29137516021728516s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 2.702755928039551s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.2684972286224365s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 0.43439507484436035s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.5752425193786621s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.31458020210266113s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.30425190925598145s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.2937357425689697s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 10.476577758789062s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.200241088867188e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.2959423065185547s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.2751619815826416s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.34438014030456543s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.29201745986938477s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.3105754852294922s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.64998459815979s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.6178500652313232s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 58.823179721832275s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.32236456871032715s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2948422431945801s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.26502203941345215s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 35.581249952316284s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.2077770233154297s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.28598666191101074s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.7403666973114014s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 19.659796237945557s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.6061902046203613s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.00014138221740722656s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.4039192199707031s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.3436756134033203s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 1704.6360993385315s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 1.1084988117218018s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 9.775161743164062e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.9073486328125e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.239776611328125e-05s
INFO | --- Analysis for data-open-ac-uk took 2007.0443427562714s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7846059799194336s
Availability | VoID file availability check for Persée in RDF took 0.0006661415100097656s
Extra | Recovery of all triples for Persée in RDF took 1.8905489444732666s
Performance | Total latancy measurement for Persée in RDF took 0.7014946937561035s
Amount of data | Number of triples check for Persée in RDF took 3.1435656547546387s
Interoperability | New terms check for Persée in RDF took 1.7688865661621094s
Versatility | Languages check for Persée in RDF took 120.62581014633179s
Interpretability | Number of blank nodes check for Persée in RDF took 0.5631518363952637s
Interpretability | RDF structures check for Persée in RDF took 0.883232831954956s
Versatility | Serialization formats check for Persée in RDF took 1.0635831356048584s
Availability | RDF dump link check for Persée in RDF took 0.3260807991027832s
License | MR license check for Persée in RDF took 1.5947265625s
License | HR license check for Persée in RDF took 39.339446783065796s
Amount of data | Number of property check for Persée in RDF took 0.13449716567993164s
Understandability | Number of label check for Persée in RDF took 1.9713900089263916s
Understandability | URI regex check for Persée in RDF took 0.7878966331481934s
Understandability | Vocabs check for Persée in RDF took 0.4735293388366699s
Verifiability | Authors check for Persée in RDF took 0.18067288398742676s
Verifiability | Publishers check for Persée in RDF took 0.12169313430786133s
Performance | Throughput check for Persée in RDF took 10.73789119720459s
Amount of data | Check the number of entities for Persée in RDF took 0.00013494491577148438s
Verifiability | Contribs. check for Persée in RDF took 0.12479853630065918s
Interlinking | sameAs chians check for Persée in RDF took 0.3085060119628906s
Interlinking | skos check for Persée in RDF took 0.8050515651702881s
Interlinking | skos check for Persée in RDF took 0.13275766372680664s
Timeliness | dataset update frequency check for Persée in RDF took 0.7855937480926514s
Currency | Creation date check for Persée in RDF took 0.5732662677764893s
Currency | Modification date check for Persée in RDF took 0.26814937591552734s
Rep.Conc. | URIs length for Persée in RDF took 3.6486496925354004s
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.13137054443359375s
Accuracy | Check Functional Property for Persée in RDF took 0.12613987922668457s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.14096379280090332s
Accuracy | Check Empty annotation labels for Persée in RDF took 1.258857250213623s
Accuracy | Check White space in annotation for Persée in RDF took 0.03815865516662598s
Accuracy | Check Datatype consistency for Persée in RDF took 0.0300142765045166s
Consistency | Disjoint class check for Persée in RDF took 0.34107542037963867s
Consistency | Check Misplaced properties for Persée in RDF took 2.6565895080566406s
Consistency | Misplaced classes for Persée in RDF took 0.21790671348571777s
Consistency | Check Ontology hijacking for Persée in RDF took 1.8395485877990723s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.2028279304504395s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.7377355098724365s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03295731544494629s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.13849091529846191s
Security | Sign check for Persée in RDF took 0.7443146705627441s
Availability | Check URIs Dereferenciability for Persée in RDF took 1465.8557577133179s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.4155151844024658s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00012350082397460938s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 8.344650268554688e-06s
INFO | --- Analysis for data-persee-fr took 1713.9553864002228s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.1961669921875e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.28365540504455566s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020322561264038086s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 2.7418136596679688e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 8.58306884765625e-06s
INFO | --- Analysis for data-southampton-ac-uk took 4.480099678039551s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.8262858390808105s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.3065307140350342s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011157989501953125s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 8.106231689453125e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 10.101436614990234s
Availability | SPARQL endpoint availability check for Open Data Web took 0.26720666885375977s
Availability | VoID file availability check for Open Data Web took 0.000244140625s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.33077192306518555s
Reputation | Calculation of the PageRank for Open Data Web took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.0279159545898438e-05s
Believability | Calculation of trust value for Open Data Web took 7.867813110351562e-06s
INFO | --- Analysis for data.odw.tw took 3.971440553665161s
Availability | SPARQL endpoint availability check for DataFAQs took 4.220008850097656e-05s
Availability | VoID file availability check for DataFAQs took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.603550910949707s
Reputation | Calculation of the PageRank for DataFAQs took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.0517578125e-05s
Believability | Calculation of trust value for DataFAQs took 5.7220458984375e-06s
INFO | --- Analysis for datafaqs took 3.490541934967041s
Availability | SPARQL endpoint availability check for datahub took 4.1961669921875e-05s
Availability | VoID file availability check for datahub took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for datahub took 0.2905747890472412s
Reputation | Calculation of the PageRank for datahub took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for datahub took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for datahub took 4.649162292480469e-05s
Believability | Calculation of trust value for datahub took 6.67572021484375e-06s
INFO | --- Analysis for datahub took 3.7793474197387695s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 6.229783058166504s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0008025169372558594s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.2821533679962158s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 2.8848648071289062e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 9.059906005859375e-06s
INFO | --- Analysis for datahub-kr-datamap took 16.542108058929443s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.5347013473510742s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2674903869628906s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.2479248046875e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.344650268554688e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 6.019144773483276s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.357689380645752s
Availability | VoID file availability check for datos-artium-org took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.2785356044769287s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007450580596923828s
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 166.30037307739258s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 4.755159616470337s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.28356361389160156s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.033348083496094e-05s
Believability | Calculation of trust value for Datos.bcn.cl took 5.245208740234375e-06s
INFO | --- Analysis for datos-bcn-cl took 15.53890585899353s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.44537353515625s
Availability | VoID file availability check for datos.bne.es took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.2940330505371094s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020328283309936523s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00010991096496582031s
Believability | Calculation of trust value for datos.bne.es took 9.775161743164062e-06s
INFO | --- Analysis for datos-bne-es took 4.4898011684417725s
Availability | SPARQL endpoint availability check for dbacademic took 0.17052626609802246s
Availability | VoID file availability check for dbacademic took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for dbacademic took 0.27660250663757324s
Reputation | Calculation of the PageRank for dbacademic took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for dbacademic took 2.765655517578125e-05s
Believability | Calculation of trust value for dbacademic took 4.0531158447265625e-06s
INFO | --- Analysis for dbacademic took 3.1475272178649902s
Availability | SPARQL endpoint availability check for DBkWik took 0.2763359546661377s
Availability | VoID file availability check for DBkWik took 0.0005581378936767578s
Extra | Recovery of all triples for DBkWik took 14.773221492767334s
Performance | Total latancy measurement for DBkWik took 0.4828779697418213s
Amount of data | Number of triples check for DBkWik took 4.584203481674194s
Interoperability | New terms check for DBkWik took 5.876328468322754s
Versatility | Languages check for DBkWik took 126.30861783027649s
Interpretability | Number of blank nodes check for DBkWik took 2.953566074371338s
Interpretability | RDF structures check for DBkWik took 0.2619318962097168s
Versatility | Serialization formats check for DBkWik took 0.20725655555725098s
Availability | RDF dump link check for DBkWik took 3.308009147644043s
License | MR license check for DBkWik took 0.4947352409362793s
License | HR license check for DBkWik took 61.68850541114807s
Amount of data | Number of property check for DBkWik took 0.13454270362854004s
Understandability | Number of label check for DBkWik took 2.1436264514923096s
Understandability | URI regex check for DBkWik took 0.3401312828063965s
Understandability | Vocabs check for DBkWik took 0.129133939743042s
Verifiability | Authors check for DBkWik took 0.12852835655212402s
Verifiability | Publishers check for DBkWik took 0.09820270538330078s
Performance | Throughput check for DBkWik took 10.661957263946533s
Amount of data | Check the number of entities for DBkWik took 7.510185241699219e-05s
Verifiability | Contribs. check for DBkWik took 0.12549138069152832s
Interlinking | sameAs chians check for DBkWik took 0.41589975357055664s
Interlinking | skos check for DBkWik took 0.46929216384887695s
Interlinking | skos check for DBkWik took 0.09027576446533203s
Timeliness | dataset update frequency check for DBkWik took 0.23108386993408203s
Currency | Creation date check for DBkWik took 0.501084566116333s
Currency | Modification date check for DBkWik took 0.22011852264404297s
Rep.Conc. | URIs length for DBkWik took 14.874101400375366s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.12205815315246582s
Accuracy | Check Functional Property for DBkWik took 0.3409912586212158s
Accuracy | Check Inverse Functional Property for DBkWik took 0.3155801296234131s
Accuracy | Check Empty annotation labels for DBkWik took 1.4736804962158203s
Accuracy | Check White space in annotation for DBkWik took 0.02386164665222168s
Accuracy | Check Datatype consistency for DBkWik took 0.027740001678466797s
Consistency | Disjoint class check for DBkWik took 0.12601995468139648s
Consistency | Check Misplaced properties for DBkWik took 16.18531894683838s
Consistency | Misplaced classes for DBkWik took 3.381791830062866s
Consistency | Check Ontology hijacking for DBkWik took 2.14176082611084s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.1923701763153076s
Consistency | Check Invalid usage of undefined properties for DBkWik took 15.581082820892334s
Conciseness | Check Extensional conciseness for DBkWik took 0.03324460983276367s
Conciseness | Check Intensional conciseness for DBkWik took 3.0608975887298584s
Security | Sign check for DBkWik took 0.3050239086151123s
Availability | Check URIs Dereferenciability for DBkWik took 14.02372431755066s
Completeness | Calculation of interlinking completeness for DBkWik took 0.8466851711273193s
Reputation | Calculation of the PageRank for DBkWik took 0.21197104454040527s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.724761962890625e-05s
Believability | Calculation of trust value for DBkWik took 6.9141387939453125e-06s
INFO | --- Analysis for dbkwik took 1672.03147482872s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.673004150390625e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.7155730724334717s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 44.31853008270264s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.3398561477661133s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006840229034423828s
Extra | Recovery of all triples for dblp Knowledge Graph took 69.03905296325684s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7833836078643799s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.15251445770263672s
Interoperability | New terms check for dblp Knowledge Graph took 1.7296171188354492s
Versatility | Languages check for dblp Knowledge Graph took 30.55729079246521s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.282911777496338s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.16945242881774902s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.16675949096679688s
Availability | RDF dump link check for dblp Knowledge Graph took 0.15372276306152344s
License | MR license check for dblp Knowledge Graph took 0.14586281776428223s
License | HR license check for dblp Knowledge Graph took 30.156410932540894s
Amount of data | Number of property check for dblp Knowledge Graph took 0.15906620025634766s
Understandability | Number of label check for dblp Knowledge Graph took 0.538947582244873s
Understandability | URI regex check for dblp Knowledge Graph took 0.2813582420349121s
Understandability | Vocabs check for dblp Knowledge Graph took 0.18480920791625977s
Verifiability | Authors check for dblp Knowledge Graph took 0.18335652351379395s
Verifiability | Publishers check for dblp Knowledge Graph took 0.16218829154968262s
Performance | Throughput check for dblp Knowledge Graph took 11.48325800895691s
Amount of data | Check the number of entities for dblp Knowledge Graph took 6.866455078125e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.18008208274841309s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.23611998558044434s
Interlinking | skos check for dblp Knowledge Graph took 0.16344308853149414s
Interlinking | skos check for dblp Knowledge Graph took 0.1354060173034668s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.17783784866333008s
Currency | Creation date check for dblp Knowledge Graph took 0.34317588806152344s
Currency | Modification date check for dblp Knowledge Graph took 0.2700979709625244s
Rep.Conc. | URIs length for dblp Knowledge Graph took 22.618659734725952s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.21992874145507812s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.14943313598632812s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.14919495582580566s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 19.84919261932373s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.103132963180542s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.15219616889953613s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.2926642894744873s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 23.95833730697632s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 1.3277301788330078s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 0.0001468658447265625s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.15240025520324707s
Security | Sign check for dblp Knowledge Graph took 0.17603135108947754s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.8523356914520264s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.0967254638671875e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 2.1457672119140625e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 9.775161743164062e-06s
INFO | --- Analysis for dblp-kg took 289.35425066947937s
Availability | SPARQL endpoint availability check for dbnary took 0.32544994354248047s
Availability | VoID file availability check for dbnary took 0.0003750324249267578s
Extra | Recovery of all triples for dbnary took 1.9600660800933838s
Performance | Total latancy measurement for dbnary took 0.41840600967407227s
Amount of data | Number of triples check for dbnary took 1.3691134452819824s
Interoperability | New terms check for dbnary took 3.6075782775878906s
Versatility | Languages check for dbnary took 60.112971782684326s
Interpretability | Number of blank nodes check for dbnary took 3.8249013423919678s
Security | Check HTTPS for dbnary took 0.1927814483642578s
Interpretability | RDF structures check for dbnary took 0.1359860897064209s
Versatility | Serialization formats check for dbnary took 0.26790833473205566s
Availability | RDF dump link check for dbnary took 0.09198784828186035s
License | MR license check for dbnary took 0.1498572826385498s
License | HR license check for dbnary took 59.00217294692993s
Amount of data | Number of property check for dbnary took 0.12608599662780762s
Understandability | Number of label check for dbnary took 0.6163358688354492s
Understandability | URI regex check for dbnary took 0.17169570922851562s
Understandability | Vocabs check for dbnary took 0.25087618827819824s
Verifiability | Authors check for dbnary took 0.08073973655700684s
Verifiability | Publishers check for dbnary took 0.0786745548248291s
Performance | Throughput check for dbnary took 10.568224906921387s
Amount of data | Check the number of entities for dbnary took 8.654594421386719e-05s
Verifiability | Contribs. check for dbnary took 0.07833695411682129s
Interlinking | sameAs chians check for dbnary took 0.11458539962768555s
Interlinking | skos check for dbnary took 0.22603845596313477s
Interlinking | skos check for dbnary took 0.07757902145385742s
Timeliness | dataset update frequency check for dbnary took 0.15355873107910156s
Currency | Creation date check for dbnary took 0.196458101272583s
Currency | Modification date check for dbnary took 0.1930544376373291s
Rep.Conc. | URIs length for dbnary took 11.666891098022461s
Interoperability | New vocabularies check for dbnary took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.11153721809387207s
Accuracy | Check Functional Property for dbnary took 0.15482544898986816s
Accuracy | Check Inverse Functional Property for dbnary took 0.12594008445739746s
Accuracy | Check Empty annotation labels for dbnary took 0.5216314792633057s
Accuracy | Check White space in annotation for dbnary took 0.025363683700561523s
Accuracy | Check Datatype consistency for dbnary took 0.02721548080444336s
Consistency | Disjoint class check for dbnary took 0.15051674842834473s
Consistency | Check Misplaced properties for dbnary took 9.144911050796509s
Consistency | Misplaced classes for dbnary took 0.24574851989746094s
Consistency | Check Ontology hijacking for dbnary took 1.9291813373565674s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.2450783252716064s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.124390840530396s
Conciseness | Check Extensional conciseness for dbnary took 0.03140902519226074s
Conciseness | Check Intensional conciseness for dbnary took 0.19113755226135254s
Security | Sign check for dbnary took 0.10003018379211426s
Availability | Check URIs Dereferenciability for dbnary took 11.516219854354858s
Completeness | Calculation of interlinking completeness for dbnary took 0.7151050567626953s
Reputation | Calculation of the PageRank for dbnary took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for dbnary took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for dbnary took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.6689300537109375e-06s
Believability | Calculation of trust value for dbnary took 8.106231689453125e-06s
INFO | --- Analysis for dbnary took 309.38012886047363s
Availability | SPARQL endpoint availability check for DBpedia took 0.890333890914917s
Availability | VoID file availability check for DBpedia took 0.0003364086151123047s
Extra | Recovery of all triples for DBpedia took 0.21921730041503906s
Performance | Total latancy measurement for DBpedia took 1.0223853588104248s
Amount of data | Number of triples check for DBpedia took 0.7033464908599854s
Interoperability | New terms check for DBpedia took 6.119029998779297s
Versatility | Languages check for DBpedia took 32.44939947128296s
Interpretability | Number of blank nodes check for DBpedia took 0.7932157516479492s
Security | Check HTTPS for DBpedia took 0.12392067909240723s
Interpretability | RDF structures check for DBpedia took 0.6250801086425781s
Versatility | Serialization formats check for DBpedia took 0.3224201202392578s
Availability | RDF dump link check for DBpedia took 0.2082509994506836s
License | MR license check for DBpedia took 1.0754854679107666s
License | HR license check for DBpedia took 32.11523938179016s
Amount of data | Number of property check for DBpedia took 0.21312189102172852s
Understandability | Number of label check for DBpedia took 3.211320638656616s
Understandability | URI regex check for DBpedia took 0.7271835803985596s
Understandability | Vocabs check for DBpedia took 0.3892805576324463s
Verifiability | Authors check for DBpedia took 0.2172691822052002s
Verifiability | Publishers check for DBpedia took 0.21097445487976074s
Amount of data | Check the number of entities for DBpedia took 6.985664367675781e-05s
Verifiability | Contribs. check for DBpedia took 0.3781616687774658s
Interlinking | sameAs chians check for DBpedia took 2.3582990169525146s
Interlinking | skos check for DBpedia took 0.7440917491912842s
Interlinking | skos check for DBpedia took 0.21175718307495117s
Timeliness | dataset update frequency check for DBpedia took 0.23783588409423828s
Currency | Creation date check for DBpedia took 0.45774173736572266s
Currency | Modification date check for DBpedia took 0.7108476161956787s
Rep.Conc. | URIs length for DBpedia took 32.13292050361633s
Interoperability | New vocabularies check for DBpedia took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.20514345169067383s
Accuracy | Check Functional Property for DBpedia took 0.3312656879425049s
Accuracy | Check Empty annotation labels for DBpedia took 3.1340572834014893s
Accuracy | Check White space in annotation for DBpedia took 0.03124547004699707s
Consistency | Disjoint class check for DBpedia took 0.20920968055725098s
Consistency | Check Misplaced properties for DBpedia took 0.5254144668579102s
Consistency | Misplaced classes for DBpedia took 1.6194870471954346s
Consistency | Check Ontology hijacking for DBpedia took 2.3140432834625244s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.3877508640289307s
Conciseness | Check Extensional conciseness for DBpedia took 0.0001418590545654297s
Conciseness | Check Intensional conciseness for DBpedia took 4.51476526260376s
Security | Sign check for DBpedia took 0.21731996536254883s
Availability | Check URIs Dereferenciability for DBpedia took 6176.973896741867s
Completeness | Calculation of interlinking completeness for DBpedia took 1.561089038848877s
Reputation | Calculation of the PageRank for DBpedia took 0.02092719078063965s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009300708770751953s
Interoperability | Check the re-using of existing vocabs for DBpedia took 9.5367431640625e-07s
Believability | Calculation of trust value for DBpedia took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia took 6340.092711687088s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 7.772445678710938e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0003476142883300781s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.2877058982849121s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.794929504394531e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.3589859008789062e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 9.356568098068237s
Availability | SPARQL endpoint availability check for DBpedia Commons took 5.009711265563965s
Availability | VoID file availability check for DBpedia Commons took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.7060480117797852s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.723403930664062e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-commons took 15.009934663772583s
Availability | SPARQL endpoint availability check for DBpedia in German took 5.4836273193359375e-05s
Availability | VoID file availability check for DBpedia in German took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.273975133895874s
Reputation | Calculation of the PageRank for DBpedia in German took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.413459777832031e-05s
Believability | Calculation of trust value for DBpedia in German took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-de took 3.552504539489746s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.937933683395386s
Availability | VoID file availability check for DBpedia in Greek took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.28863048553466797s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00020194053649902344s
Believability | Calculation of trust value for DBpedia in Greek took 3.814697265625e-06s
INFO | --- Analysis for dbpedia-el took 47.07422614097595s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.5750930309295654s
Availability | VoID file availability check for DBpedia in Spanish took 0.0005819797515869141s
Extra | Recovery of all triples for DBpedia in Spanish took 4.870687961578369s
Performance | Total latancy measurement for DBpedia in Spanish took 1.674597978591919s
Amount of data | Number of triples check for DBpedia in Spanish took 6.847779989242554s
Interoperability | New terms check for DBpedia in Spanish took 3.0269811153411865s
Versatility | Languages check for DBpedia in Spanish took 30.405792951583862s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.5056560039520264s
Security | Check HTTPS for DBpedia in Spanish took 0.1955859661102295s
Interpretability | RDF structures check for DBpedia in Spanish took 1.7485101222991943s
Versatility | Serialization formats check for DBpedia in Spanish took 0.7829654216766357s
Availability | RDF dump link check for DBpedia in Spanish took 0.5073692798614502s
License | MR license check for DBpedia in Spanish took 1.5790927410125732s
License | HR license check for DBpedia in Spanish took 30.41640615463257s
Amount of data | Number of property check for DBpedia in Spanish took 0.41370654106140137s
Understandability | Number of label check for DBpedia in Spanish took 2.9685773849487305s
Understandability | URI regex check for DBpedia in Spanish took 1.0398509502410889s
Understandability | Vocabs check for DBpedia in Spanish took 0.6448826789855957s
Verifiability | Authors check for DBpedia in Spanish took 0.7160670757293701s
Verifiability | Publishers check for DBpedia in Spanish took 0.5947272777557373s
Performance | Throughput check for DBpedia in Spanish took 12.567238569259644s
Amount of data | Check the number of entities for DBpedia in Spanish took 6.818771362304688e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.7443647384643555s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.6812171936035156s
Interlinking | skos check for DBpedia in Spanish took 1.1590516567230225s
Interlinking | skos check for DBpedia in Spanish took 0.3101963996887207s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.5479700565338135s
Currency | Creation date check for DBpedia in Spanish took 1.0919697284698486s
Currency | Modification date check for DBpedia in Spanish took 0.8165228366851807s
Rep.Conc. | URIs length for DBpedia in Spanish took 8.648640632629395s
Interoperability | New vocabularies check for DBpedia in Spanish took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.395794153213501s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.558098554611206s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.5664997100830078s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.8919787406921387s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.030782222747802734s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.027136802673339844s
Consistency | Disjoint class check for DBpedia in Spanish took 0.41528773307800293s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.759973764419556s
Consistency | Misplaced classes for DBpedia in Spanish took 1.4592952728271484s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.600703477859497s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.1462433338165283s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 7.154595136642456s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.032785892486572266s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.981323003768921s
Security | Sign check for DBpedia in Spanish took 0.41600608825683594s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 12.766196727752686s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.2764770984649658s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.024816036224365234s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-es took 643.8511061668396s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.3728773593902588s
Availability | VoID file availability check for DBpedia in Basque took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.2840611934661865s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 2.765655517578125e-05s
Believability | Calculation of trust value for DBpedia in Basque took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-eu took 9.057891845703125s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.1934056282043457s
Availability | VoID file availability check for DBpedia in French took 0.0006144046783447266s
Extra | Recovery of all triples for DBpedia in French took 352.2539339065552s
Performance | Total latancy measurement for DBpedia in French took 0.4494941234588623s
Amount of data | Number of triples check for DBpedia in French took 8.736544609069824s
Interoperability | New terms check for DBpedia in French took 7.320104122161865s
Versatility | Languages check for DBpedia in French took 300.0583715438843s
Interpretability | Number of blank nodes check for DBpedia in French took 2.335784435272217s
Interpretability | RDF structures check for DBpedia in French took 2.0306708812713623s
Versatility | Serialization formats check for DBpedia in French took 1.3634045124053955s
Availability | RDF dump link check for DBpedia in French took 7.8209898471832275s
License | MR license check for DBpedia in French took 2.024442672729492s
License | HR license check for DBpedia in French took 300.1043105125427s
Amount of data | Number of property check for DBpedia in French took 0.4366159439086914s
Understandability | Number of label check for DBpedia in French took 3.1755895614624023s
Understandability | URI regex check for DBpedia in French took 0.3410153388977051s
Understandability | Vocabs check for DBpedia in French took 0.2716031074523926s
Verifiability | Authors check for DBpedia in French took 0.5476861000061035s
Verifiability | Publishers check for DBpedia in French took 0.15106582641601562s
Performance | Throughput check for DBpedia in French took 10.477599143981934s
Amount of data | Check the number of entities for DBpedia in French took 2.1582376956939697s
Verifiability | Contribs. check for DBpedia in French took 0.14479923248291016s
Interlinking | sameAs chians check for DBpedia in French took 1.107266902923584s
Interlinking | skos check for DBpedia in French took 0.310788631439209s
Interlinking | skos check for DBpedia in French took 0.0825960636138916s
Timeliness | dataset update frequency check for DBpedia in French took 0.5317976474761963s
Currency | Creation date check for DBpedia in French took 0.3506476879119873s
Currency | Modification date check for DBpedia in French took 0.2150406837463379s
Rep.Conc. | URIs length for DBpedia in French took 160.27252173423767s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.11430239677429199s
Accuracy | Check Functional Property for DBpedia in French took 0.14550447463989258s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.11546540260314941s
Accuracy | Check Empty annotation labels for DBpedia in French took 47.62579798698425s
Accuracy | Check White space in annotation for DBpedia in French took 3.081599235534668s
Accuracy | Check Datatype consistency for DBpedia in French took 2.7209463119506836s
Consistency | Disjoint class check for DBpedia in French took 0.22933340072631836s
Consistency | Check Misplaced properties for DBpedia in French took 8.054670810699463s
Consistency | Misplaced classes for DBpedia in French took 9.883018493652344s
Consistency | Check Ontology hijacking for DBpedia in French took 65.22175884246826s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.279125452041626s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 8.333272457122803s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.0076417922973633s
Conciseness | Check Intensional conciseness for DBpedia in French took 4.0176005363464355s
Security | Sign check for DBpedia in French took 0.34761548042297363s
Availability | Check URIs Dereferenciability for DBpedia in French took 1414.3251073360443s
Completeness | Calculation of interlinking completeness for DBpedia in French took 1.6359047889709473s
Reputation | Calculation of the PageRank for DBpedia in French took 0.022055387496948242s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00017905235290527344s
Believability | Calculation of trust value for DBpedia in French took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-fr took 2999.7490561008453s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9960298538208008s
Availability | VoID file availability check for DBpedia in Japanese took 4.155234336853027s
Extra | Recovery of all triples for DBpedia in Japanese took 8.822821855545044s
Performance | Total latancy measurement for DBpedia in Japanese took 6.766617774963379s
Amount of data | Number of triples check for DBpedia in Japanese took 34.76420187950134s
Interoperability | New terms check for DBpedia in Japanese took 17.545069456100464s
Versatility | Languages check for DBpedia in Japanese took 1.3485732078552246s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3719840049743652s
Security | Check HTTPS for DBpedia in Japanese took 0.8155171871185303s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3963868618011475s
Versatility | Serialization formats check for DBpedia in Japanese took 1.404691219329834s
Availability | RDF dump link check for DBpedia in Japanese took 1.3549714088439941s
License | MR license check for DBpedia in Japanese took 1.3954112529754639s
License | HR license check for DBpedia in Japanese took 121.35322833061218s
Amount of data | Number of property check for DBpedia in Japanese took 1.3663718700408936s
Understandability | Number of label check for DBpedia in Japanese took 8.470673561096191s
Understandability | URI regex check for DBpedia in Japanese took 2.7114195823669434s
Understandability | Vocabs check for DBpedia in Japanese took 1.3572266101837158s
Verifiability | Authors check for DBpedia in Japanese took 1.364020586013794s
Verifiability | Publishers check for DBpedia in Japanese took 1.3551926612854004s
Performance | Throughput check for DBpedia in Japanese took 13.505087614059448s
Amount of data | Check the number of entities for DBpedia in Japanese took 8.177757263183594e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.5321955680847168s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.3945229053497314s
Interlinking | skos check for DBpedia in Japanese took 1.3519997596740723s
Interlinking | skos check for DBpedia in Japanese took 1.3549461364746094s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.366441011428833s
Currency | Creation date check for DBpedia in Japanese took 2.8829245567321777s
Currency | Modification date check for DBpedia in Japanese took 2.7112748622894287s
Rep.Conc. | URIs length for DBpedia in Japanese took 139.89029622077942s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3858184814453125s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3784630298614502s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3776497840881348s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 6.371825218200684s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.025899171829223633s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.028516054153442383s
Consistency | Disjoint class check for DBpedia in Japanese took 1.491041660308838s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.71156811714172s
Consistency | Misplaced classes for DBpedia in Japanese took 3.7393486499786377s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.9373064041137695s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2594127655029297s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.61317586898804s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03243255615234375s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 5.17069149017334s
Security | Sign check for DBpedia in Japanese took 1.3543143272399902s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 9.913033485412598s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.8890116214752197s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00011372566223144531s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-ja took 1193.0727043151855s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.410743713378906e-05s
Availability | VoID file availability check for dbpedia lite took 0.00039196014404296875s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.29735803604125977s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.894371032714844e-05s
Believability | Calculation of trust value for dbpedia lite took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-lite took 24.331732273101807s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.124641418457031e-05s
Availability | VoID file availability check for DBpedia-Live took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.2937498092651367s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 2.956390380859375e-05s
Believability | Calculation of trust value for DBpedia-Live took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-live took 3.9804847240448s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2868080139160156s
Availability | VoID file availability check for DBpedia in Dutch took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2904994487762451s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001647472381591797s
Believability | Calculation of trust value for DBpedia in Dutch took 4.291534423828125e-06s
INFO | --- Analysis for dbpedia-nl took 5.359210729598999s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 30.11678957939148s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.285902738571167s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.845329284667969e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-pt took 72.66393828392029s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 8.893013000488281e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.2868032455444336s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.361701965332031e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-spotlight took 4.361252546310425s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.410743713378906e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.28766727447509766s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007131099700927734s
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 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 15.100937366485596s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.28581976890563965s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 2.9325485229492188e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.589324712753296s
Availability | SPARQL endpoint availability check for DBpedia took 6.628036499023438e-05s
Availability | VoID file availability check for DBpedia took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for DBpedia took 0.29070472717285156s
Reputation | Calculation of the PageRank for DBpedia took 0.020174503326416016s
Interlinking | Calculation of Degree of Connection for DBpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.0279159545898438e-05s
Believability | Calculation of trust value for DBpedia took 1.1682510375976562e-05s
INFO | --- Analysis for dbpedia_ took 3.0843348503112793s
Availability | SPARQL endpoint availability check for DBTropes took 4.267692565917969e-05s
Availability | VoID file availability check for DBTropes took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for DBTropes took 0.2907135486602783s
Reputation | Calculation of the PageRank for DBTropes took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DBTropes took 8.940696716308594e-05s
Believability | Calculation of trust value for DBTropes took 6.198883056640625e-06s
INFO | --- Analysis for dbtropes took 3.4847404956817627s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.267692565917969e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.26757073402404785s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020359516143798828s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007359981536865234s
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 8.821487426757812e-06s
INFO | --- Analysis for dbtune took 3.111130714416504s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 6.628036499023438e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2872498035430908s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.459785461425781e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.764269828796387s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.482269287109375e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.2920355796813965s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.528594970703125e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.911029100418091s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.694803237915039s
Availability | VoID file availability check for DBTune.org/classical took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.2859041690826416s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020795106887817383s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.581710815429688e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.62939453125e-06s
INFO | --- Analysis for dbtune-classical took 22.299068927764893s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.281932830810547s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2880096435546875s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.021973609924316406s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0012259483337402344s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 9.036064147949219e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 26.8806209564209s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.28557300567627s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2844393253326416s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.937980651855469e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 8.106231689453125e-06s
INFO | --- Analysis for dbtune-magnatune took 24.547165870666504s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.28990626335144s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.2946450710296631s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010609626770019531s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 5.9604644775390625e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.873966932296753s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.303778886795044s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.28498315811157227s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.364418029785156e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-myspace took 17.882100343704224s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.31774163246154785s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.075599670410156e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 6.4373016357421875e-06s
INFO | --- Analysis for dclg-openuplabs took 3.2446935176849365s
Availability | SPARQL endpoint availability check for data.dcs took 5.650520324707031e-05s
Availability | VoID file availability check for data.dcs took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for data.dcs took 0.28394651412963867s
Reputation | Calculation of the PageRank for data.dcs took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.604194641113281e-05s
Believability | Calculation of trust value for data.dcs took 6.4373016357421875e-06s
INFO | --- Analysis for dcs-sheffield took 2.72587251663208s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 5.364418029785156e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.2873191833496094s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 2.956390380859375e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 9.298324584960938e-06s
INFO | --- Analysis for de-budget took 3.1518735885620117s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 5.054473876953125e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.3016092777252197s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.719329833984375e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.152557373046875e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.484488248825073s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.363059997558594e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.2897317409515381s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.4345855712890625e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 6.9141387939453125e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.8755271434783936s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.291534423828125e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.2962460517883301s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.02015399932861328s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 2.9325485229492188e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 3.252647638320923s
Availability | SPARQL endpoint availability check for Demografie took 4.267692565917969e-05s
Availability | VoID file availability check for Demografie took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Demografie took 0.28896069526672363s
Reputation | Calculation of the PageRank for Demografie took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.9802322387695312e-05s
Believability | Calculation of trust value for Demografie took 6.9141387939453125e-06s
INFO | --- Analysis for demografie took 3.253018379211426s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.3392181396484375e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.00048828125s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.28685927391052246s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020412445068359375s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.457069396972656e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 7.3909759521484375e-06s
INFO | --- Analysis for desaparecidos took 2.9809513092041016s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.220008850097656e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2886648178100586s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02016901969909668s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.870529174804688e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 7.3909759521484375e-06s
INFO | --- Analysis for deustoentrepreneurship took 4.450164318084717s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.3392181396484375e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2852332592010498s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.0204312801361084s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010395050048828125s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 8.106231689453125e-06s
INFO | --- Analysis for deustotech took 4.687122583389282s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.5152900218963623s
Availability | VoID file availability check for Deutsche Biographie took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.29791855812072754s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.719329833984375e-05s
Believability | Calculation of trust value for Deutsche Biographie took 6.9141387939453125e-06s
INFO | --- Analysis for deutsche-biographie took 4.572666168212891s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 5.054473876953125e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.3045177459716797s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.2928924560546875e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 6.9141387939453125e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 7.702161550521851s
Availability | SPARQL endpoint availability check for dev8d took 4.410743713378906e-05s
Availability | VoID file availability check for dev8d took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for dev8d took 0.2899434566497803s
Reputation | Calculation of the PageRank for dev8d took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.937980651855469e-05s
Believability | Calculation of trust value for dev8d took 6.9141387939453125e-06s
INFO | --- Analysis for dev8d took 2.9786577224731445s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.10843515396118s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.302567720413208s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 6.365776062011719e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 8.344650268554688e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.78635501861572s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.935264587402344e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.3055698871612549s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.0279159545898438e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 6.198883056640625e-06s
INFO | --- Analysis for DHSVM took 18.129891633987427s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.76837158203125e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.2877469062805176s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020975589752197266s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.170967102050781e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 1.8358230590820312e-05s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 3.145855665206909s
Availability | SPARQL endpoint availability check for Diavgeia took 4.220008850097656e-05s
Availability | VoID file availability check for Diavgeia took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.28756165504455566s
Reputation | Calculation of the PageRank for Diavgeia took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.273124694824219e-05s
Believability | Calculation of trust value for Diavgeia took 8.344650268554688e-06s
INFO | --- Analysis for diavgeia took 7.822457313537598s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.177757263183594e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.2881031036376953s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02006387710571289s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011682510375976562s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for didactalia took 9.440945625305176s
Availability | SPARQL endpoint availability check for diigo.feed took 4.649162292480469e-05s
Availability | VoID file availability check for diigo.feed took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.26715755462646484s
Reputation | Calculation of the PageRank for diigo.feed took 0.02033400535583496s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.8848648071289062e-05s
Believability | Calculation of trust value for diigo.feed took 7.3909759521484375e-06s
INFO | --- Analysis for diigo-feed took 3.1375091075897217s
Availability | SPARQL endpoint availability check for DisGeNET took 1.0037612915039062s
Availability | VoID file availability check for DisGeNET took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.28835463523864746s
Reputation | Calculation of the PageRank for DisGeNET took 0.025765657424926758s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0008895397186279297s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00022554397583007812s
Believability | Calculation of trust value for DisGeNET took 6.67572021484375e-06s
INFO | --- Analysis for disgenet took 9.223528623580933s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.3032689094543457s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.9087066650390625e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 8.106231689453125e-06s
INFO | --- Analysis for disk took 3.142265796661377s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.363059997558594e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.28416013717651367s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 2.7894973754882812e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 1.049041748046875e-05s
INFO | --- Analysis for distritos-zaragoza took 3.1188254356384277s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.38690185546875e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007562637329101562s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.28592371940612793s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020175457000732422s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 2.8371810913085938e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 6.9141387939453125e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 9.324901342391968s
Availability | SPARQL endpoint availability check for DM2E took 4.2438507080078125e-05s
Availability | VoID file availability check for DM2E took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for DM2E took 0.2852962017059326s
Reputation | Calculation of the PageRank for DM2E took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010752677917480469s
Believability | Calculation of trust value for DM2E took 6.67572021484375e-06s
INFO | --- Analysis for dm2e took 3.2849161624908447s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.124641418457031e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.28844451904296875s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.021041154861450195s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 2.956390380859375e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 6.198883056640625e-06s
INFO | --- Analysis for dmoz_rdf_dump took 3.136073589324951s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.8497347831726074s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.3409082889556885s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015091896057128906s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 6.4373016357421875e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 11.475678205490112s
Availability | SPARQL endpoint availability check for DOAP Store took 4.124641418457031e-05s
Availability | VoID file availability check for DOAP Store took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.2767336368560791s
Reputation | Calculation of the PageRank for DOAP Store took 0.020254850387573242s
Interlinking | Calculation of Degree of Connection for DOAP Store took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.0040740966796875e-05s
Believability | Calculation of trust value for DOAP Store took 7.152557373046875e-06s
INFO | --- Analysis for doap_store took 3.132685661315918s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.3392181396484375e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.42027950286865234s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.079673767089844e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 4.5299530029296875e-06s
INFO | --- Analysis for doi took 8.53293776512146s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.3392181396484375e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.28626251220703125s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.9325485229492188e-05s
Believability | Calculation of trust value for Driggu Florentino took 5.9604644775390625e-06s
INFO | --- Analysis for Driggu took 3.386195659637451s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.075387477874756s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.2919497489929199s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.6716461181640625e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 7.62939453125e-06s
INFO | --- Analysis for drug-data-hifm took 37.76939606666565s
Availability | SPARQL endpoint availability check for dspace took 4.315376281738281e-05s
Availability | VoID file availability check for dspace took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for dspace took 0.2924649715423584s
Reputation | Calculation of the PageRank for dspace took 0.02190566062927246s
Interlinking | Calculation of Degree of Connection for dspace took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for dspace took 0.0011026859283447266s
Interlinking | Calculation of Clustering coefficient for dspace took 4.124641418457031e-05s
Believability | Calculation of trust value for dspace took 7.62939453125e-06s
INFO | --- Analysis for dspace took 3.0631909370422363s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.1961669921875e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2750284671783447s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.075599670410156e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 6.9141387939453125e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.9982187747955322s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 272.18009543418884s
Availability | VoID file availability check for MetaLex Document Server took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.2794501781463623s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 4.220008850097656e-05s
Believability | Calculation of trust value for MetaLex Document Server took 6.198883056640625e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.5587019920349s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.7225439548492432s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.29148054122924805s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.673004150390625e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 6.67572021484375e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 14.13951563835144s
Availability | SPARQL endpoint availability check for DWS-Group took 4.482269287109375e-05s
Availability | VoID file availability check for DWS-Group took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2935903072357178s
Reputation | Calculation of the PageRank for DWS-Group took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for DWS-Group took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010156631469726562s
Believability | Calculation of trust value for DWS-Group took 6.9141387939453125e-06s
INFO | --- Analysis for dws-group took 2.7154297828674316s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 5.602836608886719e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.27783751487731934s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020334720611572266s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.075599670410156e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 6.67572021484375e-06s
INFO | --- Analysis for E1 took 4.695664644241333s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.0736379623413086s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.28167104721069336s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011682510375976562s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-alaska took 3.143610954284668s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.04801797866821289s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2831389904022217s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.626678466796875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-cau took 2.666651725769043s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.038532257080078125s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.29165196418762207s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02013397216796875s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.318092346191406e-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 3.0785958766937256s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.047743797302246094s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.29059672355651855s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.72747802734375e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.667018175125122s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.04372715950012207s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.30200815200805664s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 3.814697265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0009889602661132812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00016450881958007812s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.6905736923217773s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04772639274597168s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2880861759185791s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 9.322166442871094e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-famu took 2.7420337200164795s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04755210876464844s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.30571651458740234s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012874603271484375s
Believability | Calculation of trust value for eagle-i @ Harvard University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-harvard took 3.1337311267852783s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.054080963134765625s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.28859853744506836s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001239776611328125s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.694481611251831s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.04704880714416504s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0012784004211425781s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.28830432891845703s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-howard took 2.6506283283233643s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.048555612564086914s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2848947048187256s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020282745361328125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.389617919921875e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.712348222732544s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04993915557861328s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.28649377822875977s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011324882507324219s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-jsu took 2.651536226272583s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.04221630096435547s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.28773069381713867s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02063441276550293s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.886222839355469e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-meharry took 2.7153608798980713s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.033540964126586914s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2852208614349365s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010204315185546875s
Believability | Calculation of trust value for eagle-i @ Montana State University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-montana took 2.6716103553771973s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.049369096755981445s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.2835516929626465s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.021902084350585938s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0009300708770751953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 0.00012922286987304688s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-msm took 2.6356308460235596s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04784655570983887s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.28957581520080566s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001270771026611328s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.707770586013794s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.048821449279785156s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.28594422340393066s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 7.581710815429688e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-psm took 2.6587250232696533s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.05299639701843262s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.28507494926452637s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.437301635742188e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-tsu took 2.705303430557251s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.04055619239807129s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2818002700805664s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.175041198730469e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.6653876304626465s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.03799009323120117s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.2852776050567627s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010061264038085938s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.605417490005493s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04763460159301758s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.001192331314086914s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.28749895095825195s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00013446807861328125s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 5.245208740234375e-06s
INFO | --- Analysis for eagle-i-upr took 2.646627426147461s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.03311777114868164s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.28331661224365234s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 5.936622619628906e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-utep took 2.60199236869812s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.03264212608337402s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.28496599197387695s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020168781280517578s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.343292236328125e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-utsa took 2.655428647994995s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.1885209083557129s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.289581298828125s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 8.96453857421875e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.8290083408355713s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.03899335861206055s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2727670669555664s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.367134094238281e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-xula took 2.641984462738037s
Availability | SPARQL endpoint availability check for Emergency situation took 0.8839900493621826s
Availability | VoID file availability check for Emergency situation took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.30173301696777344s
Reputation | Calculation of the PageRank for Emergency situation took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.863739013671875e-05s
Believability | Calculation of trust value for Emergency situation took 1.0728836059570312e-05s
INFO | --- Analysis for Earthquake took 4.779900789260864s
Availability | SPARQL endpoint availability check for ESO took 0.7140107154846191s
Availability | VoID file availability check for ESO took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for ESO took 0.28766584396362305s
Reputation | Calculation of the PageRank for ESO took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for ESO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ESO took 8.058547973632812e-05s
Believability | Calculation of trust value for ESO took 6.198883056640625e-06s
INFO | --- Analysis for Earthquake_case took 4.404576063156128s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.3683888912200928s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2846827507019043s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010132789611816406s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 4.0531158447265625e-06s
INFO | --- Analysis for ecb-linked-data took 2.9614856243133545s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.577413320541382s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.29595398902893066s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.790855407714844e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 4.291534423828125e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 10.768174886703491s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.834028959274292s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.28482675552368164s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.890296936035156e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 6.269041061401367s
Availability | SPARQL endpoint availability check for ECLAP took 20.570356845855713s
Availability | VoID file availability check for ECLAP took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for ECLAP took 0.29159092903137207s
Reputation | Calculation of the PageRank for ECLAP took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.838539123535156e-05s
Believability | Calculation of trust value for ECLAP took 1.4066696166992188e-05s
INFO | --- Analysis for eclap took 53.214149475097656s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.38690185546875e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.28378796577453613s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.1920928955078125e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.2636184692382812e-05s
INFO | --- Analysis for ECNU-GISer took 4.702118158340454s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.649162292480469e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.28520631790161133s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.9604644775390625e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 8.106231689453125e-06s
INFO | --- Analysis for ecs took 2.6738083362579346s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 6.818771362304688e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.7940034866333008s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.147125244140625e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 8.344650268554688e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 3.6936092376708984s
Availability | SPARQL endpoint availability check for Edublogs took 5.364418029785156e-05s
Availability | VoID file availability check for Edublogs took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Edublogs took 0.299576997756958s
Reputation | Calculation of the PageRank for Edublogs took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010013580322265625s
Believability | Calculation of trust value for Edublogs took 8.344650268554688e-06s
INFO | --- Analysis for edublogs took 3.5588159561157227s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5707287788391113s
Availability | VoID file availability check for education.data.gov.uk took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.2850956916809082s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.893013000488281e-05s
Believability | Calculation of trust value for education.data.gov.uk took 4.0531158447265625e-06s
INFO | --- Analysis for education-data-gov-uk took 5.054713487625122s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.172325134277344e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.28499722480773926s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.02110147476196289s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.790855407714844e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.867813110351562e-06s
INFO | --- Analysis for education-openuplabs took 3.1091771125793457s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.82560682296753s
Availability | VoID file availability check for Educational programs - SISVU took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 1.2160003185272217s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 4.4345855712890625e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.152557373046875e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1323.1878583431244s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.8608613014221191s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.29158449172973633s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.021875381469726562s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.695487976074219e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 4.76837158203125e-06s
INFO | --- Analysis for eea took 8.855971574783325s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5980422496795654s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.28258419036865234s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 4.9114227294921875e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.0067901611328125e-06s
INFO | --- Analysis for eea-rod took 7.319669723510742s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.20670366287231445s
Availability | VoID file availability check for EEA Vocabularies took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.286912202835083s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 7.867813110351562e-05s
Believability | Calculation of trust value for EEA Vocabularies took 6.198883056640625e-06s
INFO | --- Analysis for eea-vocabularies took 5.780172109603882s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.673004150390625e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.28742146492004395s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020319223403930664s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0008411407470703125s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 6.4373016357421875e-06s
INFO | --- Analysis for ege-university-linked-open-data took 3.6882519721984863s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.46410679817199707s
Availability | VoID file availability check for E-Government Ontology took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.7312874794006348s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for E-Government Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for EGovOntology took 4.592587471008301s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6544363498687744s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005578994750976562s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.095651865005493s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.36134672164917s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0340206623077393s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8375670909881592s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.338446378707886s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.894226789474487s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0246984958648682s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2421462535858154s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2559664249420166s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.42443299293518066s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.720253944396973s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.277301549911499s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.37336158752441406s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5721137523651123s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.32691097259521484s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3344297409057617s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.31548571586608887s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.695451974868774s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.128715515136719e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3400743007659912s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.30679774284362793s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.45598554611206055s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2456352710723877s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9494404792785645s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.5950493812561035s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5462243556976318s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.933266639709473s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3188014030456543s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2992987632751465s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3656020164489746s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.055668592453003s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.027360916137695312s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.029320955276489258s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27416062355041504s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.670262575149536s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5702972412109375s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.477595329284668s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1680803298950195s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.22685694694519s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03336906433105469s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.499800443649292s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3812899589538574s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3463.5341901779175s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1959199905395508s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.173683166503906e-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 20654.245780944824s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 5.054473876953125e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2869570255279541s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020130157470703125s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010633468627929688s
Believability | Calculation of trust value for EIONET RDF Data took 4.76837158203125e-06s
INFO | --- Analysis for eionet-rdf took 4.174756050109863s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.5299530029296875e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.000244140625s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.2870783805847168s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.075599670410156e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 7.152557373046875e-06s
INFO | --- Analysis for ElgooG_ took 2.996842861175537s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.124641418457031e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.7445580959320068s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.123283386230469e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 6.198883056640625e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 3.5960607528686523s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 6.392434597015381s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.28609514236450195s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.128715515136719e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 6.67572021484375e-06s
INFO | --- Analysis for elviajero took 22.83116888999939s
Availability | SPARQL endpoint availability check for EMN took 5.340576171875e-05s
Availability | VoID file availability check for EMN took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for EMN took 0.28666234016418457s
Reputation | Calculation of the PageRank for EMN took 0.020357608795166016s
Interlinking | Calculation of Degree of Connection for EMN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for EMN took 3.838539123535156e-05s
Believability | Calculation of trust value for EMN took 7.152557373046875e-06s
INFO | --- Analysis for emn took 2.5801901817321777s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.482269287109375e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2749650478363037s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02081465721130371s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.7220458984375e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-co2emission took 2.607642650604248s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.38690185546875e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2910022735595703s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-crime took 2.5686745643615723s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.30109596252441406s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.719329833984375e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-energy took 2.6150779724121094s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.30919909477233887s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020218849182128906s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 8.630752563476562e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 8.821487426757812e-06s
INFO | --- Analysis for enakting-mortality took 2.6170291900634766s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.410743713378906e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2844364643096924s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.504753112792969e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 4.5299530029296875e-06s
INFO | --- Analysis for enakting-nhs took 2.5947930812835693s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 6.985664367675781e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.29237842559814453s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.14984130859375e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-population took 2.5933473110198975s
Availability | SPARQL endpoint availability check for Enel Shops took 4.076957702636719e-05s
Availability | VoID file availability check for Enel Shops took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2881941795349121s
Reputation | Calculation of the PageRank for Enel Shops took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.0517578125e-05s
Believability | Calculation of trust value for Enel Shops took 1.0728836059570312e-05s
INFO | --- Analysis for enel-shops took 3.1727144718170166s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.172325134277344e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.280839204788208s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.123283386230469e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 6.67572021484375e-06s
INFO | --- Analysis for energy-efficiency took 3.131308078765869s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.2850480079650879s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0010988712310791016s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.7670135498046875e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 3.148013114929199s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2829170227050781s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02014899253845215s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 3.145050525665283s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.28226661682128906s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for english-heritage-components-thesaurus took 3.099393129348755s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.28667593002319336s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.02013683319091797s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 2.765655517578125e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 3.114795684814453s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 5.078315734863281e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.28423094749450684s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020229339599609375s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 3.1879749298095703s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.287961483001709s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.02032756805419922s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.0040740966796875e-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 3.1817874908447266s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.2818613052368164s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 3.0926737785339355s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.7891736030578613s
Availability | VoID file availability check for English Heritage Periods List took 0.0007145404815673828s
Extra | Recovery of all triples for English Heritage Periods List took 0.5530877113342285s
Performance | Total latancy measurement for English Heritage Periods List took 2.2344322204589844s
Amount of data | Number of triples check for English Heritage Periods List took 0.6592824459075928s
Versatility | Languages check for English Heritage Periods List took 0.4205904006958008s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.7077007293701172s
Security | Check HTTPS for English Heritage Periods List took 0.30947017669677734s
Interpretability | RDF structures check for English Heritage Periods List took 0.39015960693359375s
Versatility | Serialization formats check for English Heritage Periods List took 0.7718288898468018s
Availability | RDF dump link check for English Heritage Periods List took 0.4792203903198242s
License | MR license check for English Heritage Periods List took 0.623138427734375s
License | HR license check for English Heritage Periods List took 0.5415585041046143s
Amount of data | Number of property check for English Heritage Periods List took 0.539304256439209s
Understandability | Number of label check for English Heritage Periods List took 0.6528763771057129s
Understandability | URI regex check for English Heritage Periods List took 0.8567004203796387s
Understandability | Vocabs check for English Heritage Periods List took 0.5052671432495117s
Verifiability | Authors check for English Heritage Periods List took 0.5321171283721924s
Verifiability | Publishers check for English Heritage Periods List took 0.44625067710876465s
Performance | Throughput check for English Heritage Periods List took 12.775627851486206s
Amount of data | Check the number of entities for English Heritage Periods List took 5.936622619628906e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.4356062412261963s
Interlinking | sameAs chians check for English Heritage Periods List took 0.46834421157836914s
Interlinking | skos check for English Heritage Periods List took 0.45311570167541504s
Interlinking | skos check for English Heritage Periods List took 0.4564700126647949s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.5099098682403564s
Currency | Creation date check for English Heritage Periods List took 0.8589584827423096s
Currency | Modification date check for English Heritage Periods List took 0.9280333518981934s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8305106163024902s
Interoperability | New vocabularies check for English Heritage Periods List took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.43401622772216797s
Accuracy | Check Functional Property for English Heritage Periods List took 0.42767906188964844s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.4505436420440674s
Consistency | Disjoint class check for English Heritage Periods List took 0.4611234664916992s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.4372677803039551s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6303186416625977s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0005767345428466797s
Security | Sign check for English Heritage Periods List took 0.4785730838775635s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.29028749465942383s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-periods-list took 64.78249931335449s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.34392762184143066s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.28365278244018555s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.1948089599609375e-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.6029202938079834s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.272061824798584s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.28184008598327637s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.3855438232421875e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.4836273193359375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 3.9794235229492188s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.410743713378906e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.2753880023956299s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020830631256103516s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.075599670410156e-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 3.097897529602051s
Availability | SPARQL endpoint availability check for English WordNet took 4.363059997558594e-05s
Availability | VoID file availability check for English WordNet took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for English WordNet took 0.28856587409973145s
Reputation | Calculation of the PageRank for English WordNet took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.409385681152344e-05s
Believability | Calculation of trust value for English WordNet took 8.58306884765625e-06s
INFO | --- Analysis for english-wordnet took 3.286876678466797s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.1961669921875e-05s
Availability | VoID file availability check for English Heritage Places took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.2834494113922119s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.147125244140625e-05s
Believability | Calculation of trust value for English Heritage Places took 6.67572021484375e-06s
INFO | --- Analysis for englishheritage_places took 3.1336002349853516s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.20418453216552734s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.27095723152160645s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007181167602539062s
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 6.4373016357421875e-06s
INFO | --- Analysis for enipedia took 2.7554919719696045s
Availability | SPARQL endpoint availability check for Enslaved.org took 6.794929504394531e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.27669572830200195s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.24249267578125e-05s
Believability | Calculation of trust value for Enslaved.org took 5.9604644775390625e-06s
INFO | --- Analysis for enslaved.org took 4.865621328353882s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.06626725196838379s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.27840471267700195s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020938873291015625s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.14984130859375e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 5.4836273193359375e-06s
INFO | --- Analysis for entice-graph took 2.633561611175537s
Availability | SPARQL endpoint availability check for Entrez Gene took 5.1975250244140625e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007979869842529297s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.3048055171966553s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.695487976074219e-05s
Believability | Calculation of trust value for Entrez Gene took 5.7220458984375e-06s
INFO | --- Analysis for entrez_gene took 29.030460119247437s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 7.891654968261719e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.296875s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020968198776245117s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.218650817871094e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene_extract took 3.125185966491699s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.3070282936096191s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.28827548027038574s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.173683166503906e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 9.298324584960938e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.96613335609436s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.361952543258667s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.29184675216674805s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.506111145019531e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for environment-data-gov-uk took 10.742706537246704s
Availability | SPARQL endpoint availability check for EARTh took 271.6080243587494s
Availability | VoID file availability check for EARTh took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for EARTh took 0.2855093479156494s
Reputation | Calculation of the PageRank for EARTh took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for EARTh took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010585784912109375s
Believability | Calculation of trust value for EARTh took 7.867813110351562e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 565.1697468757629s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 392.88019371032715s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.00039768218994140625s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.8387882709503174s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.03360104560852051s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 7.271766662597656e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0010058879852294922s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 9.512901306152344e-05s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for EO_metadata took 669.9458305835724s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.506111145019531e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.7229418754577637s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.021367311477661133s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.1948089599609375e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.811981201171875e-05s
INFO | --- Analysis for EOKP-Datasets took 5.0323920249938965s
Availability | SPARQL endpoint availability check for EPA-CDR took 8.916854858398438e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.28514552116394043s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.552436828613281e-05s
Believability | Calculation of trust value for EPA-CDR took 4.76837158203125e-06s
INFO | --- Analysis for epa-cdr took 7.874230146408081s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.2438507080078125e-05s
Availability | VoID file availability check for EPA-FRS took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.39833879470825195s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020124197006225586s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 8.821487426757812e-05s
Believability | Calculation of trust value for EPA-FRS took 5.245208740234375e-06s
INFO | --- Analysis for epa-frs took 6.45831036567688s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.410743713378906e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.3292696475982666s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020961523056030273s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.504753112792969e-05s
Believability | Calculation of trust value for EPA-RCRA took 4.76837158203125e-06s
INFO | --- Analysis for epa-rcra took 7.070713758468628s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.410743713378906e-05s
Availability | VoID file availability check for EPA-SRS took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.28285980224609375s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.605552673339844e-05s
Believability | Calculation of trust value for EPA-SRS took 4.76837158203125e-06s
INFO | --- Analysis for epa-srs took 7.288369178771973s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.3392181396484375e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.28952670097351074s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.337860107421875e-05s
Believability | Calculation of trust value for EPA-TRI took 8.821487426757812e-06s
INFO | --- Analysis for epa-tri took 5.999834060668945s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 5.459785461425781e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.28978395462036133s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.176399230957031e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 7.3909759521484375e-06s
INFO | --- Analysis for epo took 3.094709873199463s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.04228615760803223s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.27549314498901367s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0009562969207763672s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00014853477478027344s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 3.119988203048706s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5554666519165039s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.2837519645690918s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.130073547363281e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 6.67572021484375e-06s
INFO | --- Analysis for eprtr took 4.002398729324341s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 1.0429022312164307s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0008382797241210938s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.28282809257507324s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.0040740966796875e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 8.58306884765625e-06s
INFO | --- Analysis for ERAKG took 3.637266159057617s
Availability | SPARQL endpoint availability check for reg took 4.4345855712890625e-05s
Availability | VoID file availability check for reg took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for reg took 0.288590669631958s
Reputation | Calculation of the PageRank for reg took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for reg took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for reg took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for reg took 1.1205673217773438e-05s
Believability | Calculation of trust value for reg took 6.67572021484375e-06s
INFO | --- Analysis for erg took 2.5339407920837402s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.46105051040649414s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2849550247192383s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020100831985473633s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 2.765655517578125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 8.821487426757812e-06s
INFO | --- Analysis for es-msssi-drug-prices took 3.2859280109405518s
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.0006852149963378906s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2683110237121582s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.821487426757812e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.4836273193359375e-06s
INFO | --- Analysis for esd-standards took 4.345598936080933s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.38690185546875e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.28718042373657227s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 6.985664367675781e-05s
Believability | Calculation of trust value for ESD-Toolkit took 4.5299530029296875e-06s
INFO | --- Analysis for esd-toolkit took 3.6122050285339355s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.363059997558594e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.30295586585998535s
Reputation | Calculation of the PageRank for Dataset Esis took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 2.8133392333984375e-05s
Believability | Calculation of trust value for Dataset Esis took 8.821487426757812e-06s
INFO | --- Analysis for esislearning took 3.078362226486206s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.506111145019531e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2862274646759033s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020654678344726562s
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.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.0279159545898438e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 8.58306884765625e-06s
INFO | --- Analysis for ESV took 4.388553142547607s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5348997116088867s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.28753232955932617s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.440523862838745s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.344167947769165s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0007340908050537109s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.28769373893737793s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.367134094238281e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 6.67572021484375e-06s
INFO | --- Analysis for eu-agencies-bodies took 12.982714653015137s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.220008850097656e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.2843163013458252s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020331621170043945s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 2.9087066650390625e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 6.9141387939453125e-06s
INFO | --- Analysis for eu-dgt-tm took 3.1157753467559814s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.220008850097656e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.28795480728149414s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020287513732910156s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.605552673339844e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 4.76837158203125e-06s
INFO | --- Analysis for eu-institutions took 5.878532648086548s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.8011519908905029s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2920715808868408s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02022266387939453s
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.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.266334533691406e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 4.5299530029296875e-06s
INFO | --- Analysis for eu-parliament-media took 6.6560959815979s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.7817561626434326s
Availability | VoID file availability check for EU Who Is Who took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2872755527496338s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.528594970703125e-05s
Believability | Calculation of trust value for EU Who Is Who took 4.76837158203125e-06s
INFO | --- Analysis for eu-who-is-who took 9.048711776733398s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.7791829109191895s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.27349853515625s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020157814025878906s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.910064697265625e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for eumida-linked-data took 8.403065204620361s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3019537925720215s
Availability | VoID file availability check for European Nature Information System took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.28882431983947754s
Reputation | Calculation of the PageRank for European Nature Information System took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00011491775512695312s
Believability | Calculation of trust value for European Nature Information System took 7.62939453125e-06s
INFO | --- Analysis for eunis took 4.535078525543213s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 4.426784038543701s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2884087562561035s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020252227783203125s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.390975952148438e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for eur-lex-rdf took 12.63218379020691s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.7327966690063477s
Availability | VoID file availability check for Standard Eurobarometer took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.28111982345581055s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.029273986816406e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 5.4836273193359375e-06s
INFO | --- Analysis for eurobarometer-standard took 7.296753406524658s
Availability | SPARQL endpoint availability check for European Election Results took 0.7233114242553711s
Availability | VoID file availability check for European Election Results took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2849550247192383s
Reputation | Calculation of the PageRank for European Election Results took 0.02007770538330078s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.504753112792969e-05s
Believability | Calculation of trust value for European Election Results took 5.4836273193359375e-06s
INFO | --- Analysis for european-election-results took 7.430970907211304s
Availability | SPARQL endpoint availability check for EPO patents took 0.4239766597747803s
Availability | VoID file availability check for EPO patents took 0.0005350112915039062s
Extra | Recovery of all triples for EPO patents took 52.549922704696655s
Performance | Total latancy measurement for EPO patents took 0.9013233184814453s
Amount of data | Number of triples check for EPO patents took 90.22900342941284s
Versatility | Languages check for EPO patents took 120.10364651679993s
Interpretability | Number of blank nodes check for EPO patents took 90.30000305175781s
Interpretability | RDF structures check for EPO patents took 0.21766042709350586s
Versatility | Serialization formats check for EPO patents took 0.33257293701171875s
Availability | RDF dump link check for EPO patents took 0.20431184768676758s
License | MR license check for EPO patents took 0.27131056785583496s
License | HR license check for EPO patents took 90.18861198425293s
Amount of data | Number of property check for EPO patents took 0.2850961685180664s
Understandability | Number of label check for EPO patents took 90.20690703392029s
Understandability | URI regex check for EPO patents took 0.45558691024780273s
Understandability | Vocabs check for EPO patents took 0.2152411937713623s
Verifiability | Authors check for EPO patents took 0.27384185791015625s
Verifiability | Publishers check for EPO patents took 0.28196048736572266s
Performance | Throughput check for EPO patents took 11.0545334815979s
Amount of data | Check the number of entities for EPO patents took 7.486343383789062e-05s
Verifiability | Contribs. check for EPO patents took 0.21907424926757812s
Interlinking | sameAs chians check for EPO patents took 0.22730326652526855s
Interlinking | skos check for EPO patents took 0.28415465354919434s
Interlinking | skos check for EPO patents took 0.2913663387298584s
Timeliness | dataset update frequency check for EPO patents took 0.19890618324279785s
Currency | Creation date check for EPO patents took 0.46033620834350586s
Currency | Modification date check for EPO patents took 0.39299726486206055s
Rep.Conc. | URIs length for EPO patents took 156.76916980743408s
Interoperability | New vocabularies check for EPO patents took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.2077488899230957s
Accuracy | Check Empty annotation labels for EPO patents took 18.228671073913574s
Accuracy | Check White space in annotation for EPO patents took 2.9948246479034424s
Accuracy | Check Datatype consistency for EPO patents took 4.8894031047821045s
Consistency | Disjoint class check for EPO patents took 0.27121734619140625s
Consistency | Check Misplaced properties for EPO patents took 120.33317804336548s
Consistency | Check Ontology hijacking for EPO patents took 23.71122169494629s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.467785358428955s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.3970034122467s
Conciseness | Check Extensional conciseness for EPO patents took 2.814046859741211s
Conciseness | Check Intensional conciseness for EPO patents took 0.3617720603942871s
Security | Sign check for EPO patents took 0.30847668647766113s
Availability | Check URIs Dereferenciability for EPO patents took 1.6196587085723877s
Completeness | Calculation of interlinking completeness for EPO patents took 1.144911289215088s
Reputation | Calculation of the PageRank for EPO patents took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.430511474609375e-06s
Believability | Calculation of trust value for EPO patents took 6.9141387939453125e-06s
INFO | --- Analysis for European_Patent_Information took 1323.8716032505035s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.410743713378906e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.7216522693634033s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020811080932617188s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.123283386230469e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for europeana-lod took 4.41310453414917s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.506111145019531e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.32818031311035156s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 0.00011491775512695312s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 8.344650268554688e-06s
INFO | --- Analysis for europeana-lod-v1 took 113.51975965499878s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.04997849464416504s
Availability | VoID file availability check for Europeana SPARQL took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2772490978240967s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.1021575927734375e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.3909759521484375e-06s
INFO | --- Analysis for europeana-sparql took 4.424159526824951s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.0805971622467041s
Availability | VoID file availability check for EuroSentiment took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.3376164436340332s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.1484832763671875e-05s
Believability | Calculation of trust value for EuroSentiment took 8.344650268554688e-06s
INFO | --- Analysis for eurosentiment took 4.276707887649536s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.315376281738281e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2844090461730957s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.177757263183594e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.245208740234375e-06s
INFO | --- Analysis for eurostat-rdf took 17.328980445861816s
Availability | SPARQL endpoint availability check for EuroVoc took 0.38167858123779297s
Availability | VoID file availability check for EuroVoc took 0.0006639957427978516s
Extra | Recovery of all triples for EuroVoc took 112.67367315292358s
Performance | Total latancy measurement for EuroVoc took 0.6247971057891846s
Amount of data | Number of triples check for EuroVoc took 112.41377854347229s
Interoperability | New terms check for EuroVoc took 92.36639928817749s
Versatility | Languages check for EuroVoc took 300.14367055892944s
Interpretability | Number of blank nodes check for EuroVoc took 1.610670566558838s
Security | Check HTTPS for EuroVoc took 0.3609485626220703s
Interpretability | RDF structures check for EuroVoc took 0.5949139595031738s
Versatility | Serialization formats check for EuroVoc took 4.154690980911255s
Availability | RDF dump link check for EuroVoc took 0.31502294540405273s
License | MR license check for EuroVoc took 0.2738344669342041s
License | HR license check for EuroVoc took 300.08884620666504s
Amount of data | Number of property check for EuroVoc took 0.17688250541687012s
Understandability | Number of label check for EuroVoc took 7.384241342544556s
Understandability | URI regex check for EuroVoc took 0.439572811126709s
Understandability | Vocabs check for EuroVoc took 0.10425353050231934s
Verifiability | Authors check for EuroVoc took 0.3562741279602051s
Verifiability | Publishers check for EuroVoc took 0.2617042064666748s
Performance | Throughput check for EuroVoc took 10.77477216720581s
Amount of data | Check the number of entities for EuroVoc took 8.034706115722656e-05s
Verifiability | Contribs. check for EuroVoc took 0.43822407722473145s
Interlinking | sameAs chians check for EuroVoc took 9.124949932098389s
Interlinking | skos check for EuroVoc took 0.46922945976257324s
Interlinking | skos check for EuroVoc took 0.45937252044677734s
Timeliness | dataset update frequency check for EuroVoc took 0.35289430618286133s
Currency | Creation date check for EuroVoc took 0.8837957382202148s
Currency | Modification date check for EuroVoc took 0.26758313179016113s
Rep.Conc. | URIs length for EuroVoc took 464.4925904273987s
Interoperability | New vocabularies check for EuroVoc took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.18280243873596191s
Accuracy | Check Functional Property for EuroVoc took 0.20189332962036133s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.16823315620422363s
Accuracy | Check Empty annotation labels for EuroVoc took 34.39048099517822s
Accuracy | Check White space in annotation for EuroVoc took 3.1277599334716797s
Accuracy | Check Datatype consistency for EuroVoc took 2.696577787399292s
Consistency | Disjoint class check for EuroVoc took 0.18646025657653809s
Consistency | Check Misplaced properties for EuroVoc took 300.45167660713196s
Consistency | Misplaced classes for EuroVoc took 8.572291374206543s
Consistency | Check Ontology hijacking for EuroVoc took 41.04564595222473s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.5689802169799805s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.4209694862366s
Conciseness | Check Extensional conciseness for EuroVoc took 3.0110795497894287s
Conciseness | Check Intensional conciseness for EuroVoc took 0.6101434230804443s
Security | Sign check for EuroVoc took 0.1631479263305664s
Availability | Check URIs Dereferenciability for EuroVoc took 4.3199381828308105s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.7099902629852295s
Reputation | Calculation of the PageRank for EuroVoc took 0.02090930938720703s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 7.510185241699219e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 5.4836273193359375e-06s
Believability | Calculation of trust value for EuroVoc took 7.62939453125e-06s
INFO | --- Analysis for eurovoc took 15627.882200717926s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.315376281738281e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.27788543701171875s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.1961669921875e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 7.867813110351562e-06s
INFO | --- Analysis for eurovoc-in-skos took 4.473827123641968s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.410743713378906e-05s
Availability | VoID file availability check for European Television Heritage took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.2865128517150879s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 3.123283386230469e-05s
Believability | Calculation of trust value for European Television Heritage took 9.059906005859375e-06s
INFO | --- Analysis for euscreen took 3.64886736869812s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 5.936622619628906e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2914097309112549s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02152538299560547s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.507469177246094e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for euskadi-farmacias took 7.468588829040527s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7722804546356201s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.2878847122192383s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 2.9802322387695312e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 7.867813110351562e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.665941953659058s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.3821897506713867s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0010900497436523438s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2866475582122803s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.128715515136719e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 8.106231689453125e-06s
INFO | --- Analysis for eutc-productions took 6.823233604431152s
Availability | SPARQL endpoint availability check for EventMedia took 0.6104590892791748s
Availability | VoID file availability check for EventMedia took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2869455814361572s
Reputation | Calculation of the PageRank for EventMedia took 0.02025747299194336s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011181831359863281s
Believability | Calculation of trust value for EventMedia took 6.4373016357421875e-06s
INFO | --- Analysis for event-media took 14.267245531082153s
Availability | SPARQL endpoint availability check for EventKG took 4.3392181396484375e-05s
Availability | VoID file availability check for EventKG took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for EventKG took 0.3061027526855469s
Reputation | Calculation of the PageRank for EventKG took 0.02011394500732422s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.249282836914062e-05s
Believability | Calculation of trust value for EventKG took 7.152557373046875e-06s
INFO | --- Analysis for eventkg took 5.33797550201416s
Availability | SPARQL endpoint availability check for Eventseer took 0.854680061340332s
Availability | VoID file availability check for Eventseer took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Eventseer took 0.29140186309814453s
Reputation | Calculation of the PageRank for Eventseer took 0.020213603973388672s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.553794860839844e-05s
Believability | Calculation of trust value for Eventseer took 7.152557373046875e-06s
INFO | --- Analysis for eventseer took 3.526320219039917s
Availability | SPARQL endpoint availability check for Face Link took 4.3392181396484375e-05s
Availability | VoID file availability check for Face Link took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for Face Link took 0.2844088077545166s
Reputation | Calculation of the PageRank for Face Link took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Face Link took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.3855438232421875e-05s
Believability | Calculation of trust value for Face Link took 6.9141387939453125e-06s
INFO | --- Analysis for Face_Link took 2.566448926925659s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.267692565917969e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.28366875648498535s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020415544509887695s
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.0007278919219970703s
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 6.4373016357421875e-06s
INFO | --- Analysis for facebook-lids took 3.128401517868042s
Availability | SPARQL endpoint availability check for Fact Forge took 4.2438507080078125e-05s
Availability | VoID file availability check for Fact Forge took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.2851741313934326s
Reputation | Calculation of the PageRank for Fact Forge took 0.020359516143798828s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.0040740966796875e-05s
Believability | Calculation of trust value for Fact Forge took 6.198883056640625e-06s
INFO | --- Analysis for fact-forge took 3.1459150314331055s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 392.3369679450989s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2827930450439453s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.172325134277344e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for FADN_(2019) took 667.3224649429321s
Availability | SPARQL endpoint availability check for FAMEData took 6.031990051269531e-05s
Availability | VoID file availability check for FAMEData took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for FAMEData took 1.2679996490478516s
Reputation | Calculation of the PageRank for FAMEData took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.886222839355469e-05s
Believability | Calculation of trust value for FAMEData took 7.867813110351562e-06s
INFO | --- Analysis for famedata took 66.67986822128296s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.744529724121094e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.28612232208251953s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010156631469726562s
Believability | Calculation of trust value for FAO geopolitical ontology took 4.5299530029296875e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.363127708435059s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.5572299957275391s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.28797316551208496s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020174026489257812s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.942054748535156e-05s
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 3.1448733806610107s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.267692565917969e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.7483878135681152s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020173072814941406s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 2.7894973754882812e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for FAO_species took 3.906066656112671s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.43327307701111s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.3066105842590332s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.482269287109375e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 7.3909759521484375e-06s
INFO | --- Analysis for farmbio-chembl took 64.58761143684387s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.076957702636719e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.2851836681365967s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.02017498016357422s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 2.86102294921875e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 6.198883056640625e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 3.161935329437256s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 8.58306884765625e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.28858375549316406s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.71661376953125e-05s
INFO | --- Analysis for farolapp-dataset took 3.1196084022521973s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.315376281738281e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.3078339099884033s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 2.9325485229492188e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 7.3909759521484375e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 3.179964780807495s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.4345855712890625e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.3004157543182373s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020432472229003906s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.7894973754882812e-05s
Believability | Calculation of trust value for I4.0-Onto took 7.3909759521484375e-06s
INFO | --- Analysis for fatimazahra took 2.563570261001587s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.267692565917969e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.2825164794921875s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020229101181030273s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 2.8133392333984375e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 7.62939453125e-06s
INFO | --- Analysis for federal-economic-rdf took 3.1247828006744385s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.100799560546875e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.28875184059143066s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 2.9087066650390625e-05s
Believability | Calculation of trust value for Feed Wrapper took 8.106231689453125e-06s
INFO | --- Analysis for feedwrapper-lids took 3.132768154144287s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.744529724121094e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2826519012451172s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020313739776611328s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.86102294921875e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.1920928955078125e-05s
INFO | --- Analysis for FHIR_STU3 took 2.8811697959899902s
Availability | SPARQL endpoint availability check for FiESTA took 4.2438507080078125e-05s
Availability | VoID file availability check for FiESTA took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for FiESTA took 0.29760003089904785s
Reputation | Calculation of the PageRank for FiESTA took 0.02504563331604004s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for FiESTA took 4.458427429199219e-05s
Believability | Calculation of trust value for FiESTA took 7.62939453125e-06s
INFO | --- Analysis for fiesta took 12.687304496765137s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.482269287109375e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2896292209625244s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.0040740966796875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.62939453125e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.5944173336029053s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.744529724121094e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2868475914001465s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.414817810058594e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 4.76837158203125e-06s
INFO | --- Analysis for finnish-municipalities took 5.324037551879883s
Availability | SPARQL endpoint availability check for firmao took 4.124641418457031e-05s
Availability | VoID file availability check for firmao took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for firmao took 0.28769636154174805s
Reputation | Calculation of the PageRank for firmao took 0.02014446258544922s
Interlinking | Calculation of Degree of Connection for firmao took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for firmao took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for firmao took 2.8848648071289062e-05s
Believability | Calculation of trust value for firmao took 7.62939453125e-06s
INFO | --- Analysis for firmao took 3.1110281944274902s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.29964780807495117s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 3.125824451446533s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 392.1975955963135s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.2866792678833008s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.020778656005859375s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.62396240234375e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.811981201171875e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 667.174099445343s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.4345855712890625e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.7301511764526367s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 9.131431579589844e-05s
Believability | Calculation of trust value for Fishes of Texas took 6.67572021484375e-06s
INFO | --- Analysis for fishes-of-texas took 4.860770225524902s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.2438507080078125e-05s
Availability | VoID file availability check for flickr? wrappr took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.28507113456726074s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.417533874511719e-05s
Believability | Calculation of trust value for flickr? wrappr took 6.67572021484375e-06s
INFO | --- Analysis for flickr-wrappr took 3.8918778896331787s
Availability | SPARQL endpoint availability check for flickr.person took 3.981590270996094e-05s
Availability | VoID file availability check for flickr.person took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for flickr.person took 0.28815579414367676s
Reputation | Calculation of the PageRank for flickr.person took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.147125244140625e-05s
Believability | Calculation of trust value for flickr.person took 7.62939453125e-06s
INFO | --- Analysis for flickr_person took 4.420428037643433s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.100799560546875e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.7805347442626953s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.1948089599609375e-05s
Believability | Calculation of trust value for flickr.videoobject took 6.9141387939453125e-06s
INFO | --- Analysis for flickr_videoobject took 4.016180515289307s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.2438507080078125e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.28679418563842773s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.0040740966796875e-05s
Believability | Calculation of trust value for Future land use simulation model took 7.3909759521484375e-06s
INFO | --- Analysis for FLUS took 9.849445343017578s
Availability | SPARQL endpoint availability check for Fly-TED took 4.172325134277344e-05s
Availability | VoID file availability check for Fly-TED took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.28416967391967773s
Reputation | Calculation of the PageRank for Fly-TED took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.1948089599609375e-05s
Believability | Calculation of trust value for Fly-TED took 6.198883056640625e-06s
INFO | --- Analysis for fly-ted took 3.1315836906433105s
Availability | SPARQL endpoint availability check for FlyAtlas took 4.1961669921875e-05s
Availability | VoID file availability check for FlyAtlas took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.2890636920928955s
Reputation | Calculation of the PageRank for FlyAtlas took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.123283386230469e-05s
Believability | Calculation of trust value for FlyAtlas took 5.9604644775390625e-06s
INFO | --- Analysis for flyatlas took 3.160752773284912s
Availability | SPARQL endpoint availability check for Flybase took 1.9938359260559082s
Availability | VoID file availability check for Flybase took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Flybase took 0.284529447555542s
Reputation | Calculation of the PageRank for Flybase took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.504753112792969e-05s
Believability | Calculation of trust value for Flybase took 6.9141387939453125e-06s
INFO | --- Analysis for flybase took 10.667454957962036s
Availability | SPARQL endpoint availability check for Flyted took 1.231961727142334s
Availability | VoID file availability check for Flyted took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Flyted took 0.2747318744659424s
Reputation | Calculation of the PageRank for Flyted took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for Flyted took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0994415283203125e-05s
Believability | Calculation of trust value for Flyted took 6.4373016357421875e-06s
INFO | --- Analysis for flyted took 11.302606105804443s
Availability | SPARQL endpoint availability check for Foodista took 1.0676908493041992s
Availability | VoID file availability check for Foodista took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for Foodista took 0.28597450256347656s
Reputation | Calculation of the PageRank for Foodista took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9802322387695312e-05s
Believability | Calculation of trust value for Foodista took 1.1682510375976562e-05s
INFO | --- Analysis for foodista took 10.437304019927979s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.18418288230895996s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2835052013397217s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.224082946777344e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.62939453125e-06s
INFO | --- Analysis for foodpedia took 2.7986080646514893s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.3392181396484375e-05s
Availability | VoID file availability check for FORGE Course information took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.30463314056396484s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.123283386230469e-05s
Believability | Calculation of trust value for FORGE Course information took 9.298324584960938e-06s
INFO | --- Analysis for forge-course-information took 3.1394124031066895s
Availability | SPARQL endpoint availability check for FrameBase schema took 8.273124694824219e-05s
Availability | VoID file availability check for FrameBase schema took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.28546833992004395s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.7206878662109375e-05s
Believability | Calculation of trust value for FrameBase schema took 8.106231689453125e-06s
INFO | --- Analysis for framebase-schema took 3.211728811264038s
Availability | SPARQL endpoint availability check for FrameNet took 4.220008850097656e-05s
Availability | VoID file availability check for FrameNet took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for FrameNet took 0.2864186763763428s
Reputation | Calculation of the PageRank for FrameNet took 0.020529747009277344s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.1948089599609375e-05s
Believability | Calculation of trust value for FrameNet took 7.62939453125e-06s
INFO | --- Analysis for framenet took 3.1202025413513184s
Availability | SPARQL endpoint availability check for Framester took 4.9114227294921875e-05s
Availability | VoID file availability check for Framester took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Framester took 0.300703763961792s
Reputation | Calculation of the PageRank for Framester took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for Framester took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Framester took 7.486343383789062e-05s
Believability | Calculation of trust value for Framester took 7.867813110351562e-06s
INFO | --- Analysis for framester took 3.603668451309204s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.16003131866455078s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.28655505180358887s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.630752563476562e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 7.62939453125e-06s
INFO | --- Analysis for frb-linked-data took 2.814166784286499s
Availability | SPARQL endpoint availability check for Freebase took 4.553794860839844e-05s
Availability | VoID file availability check for Freebase took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Freebase took 0.30055689811706543s
Reputation | Calculation of the PageRank for Freebase took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00027489662170410156s
Believability | Calculation of trust value for Freebase took 8.106231689453125e-06s
INFO | --- Analysis for freebase took 4.688331365585327s
Availability | SPARQL endpoint availability check for Freeyork took 4.3392181396484375e-05s
Availability | VoID file availability check for Freeyork took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2879304885864258s
Reputation | Calculation of the PageRank for Freeyork took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.0001049041748046875s
Believability | Calculation of trust value for Freeyork took 7.62939453125e-06s
INFO | --- Analysis for freeyork-org took 3.217949867248535s
Availability | SPARQL endpoint availability check for French School Program took 4.00543212890625e-05s
Availability | VoID file availability check for French School Program took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for French School Program took 0.28996849060058594s
Reputation | Calculation of the PageRank for French School Program took 0.020345687866210938s
Interlinking | Calculation of Degree of Connection for French School Program took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.0994415283203125e-05s
Believability | Calculation of trust value for French School Program took 6.9141387939453125e-06s
INFO | --- Analysis for french-school-program took 3.171492576599121s
Availability | SPARQL endpoint availability check for French School System took 4.076957702636719e-05s
Availability | VoID file availability check for French School System took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for French School System took 0.31968164443969727s
Reputation | Calculation of the PageRank for French School System took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for French School System took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for French School System took 3.075599670410156e-05s
Believability | Calculation of trust value for French School System took 7.152557373046875e-06s
INFO | --- Analysis for french-school-system took 3.205256223678589s
Availability | SPARQL endpoint availability check for French TimeBank took 4.124641418457031e-05s
Availability | VoID file availability check for French TimeBank took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.29167866706848145s
Reputation | Calculation of the PageRank for French TimeBank took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.743171691894531e-05s
Believability | Calculation of trust value for French TimeBank took 1.6689300537109375e-05s
INFO | --- Analysis for french-timebank took 3.1519012451171875s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7921650409698486s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.2849273681640625s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.271766662597656e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.702894926071167s
Availability | SPARQL endpoint availability check for DailyMed took 0.7667267322540283s
Availability | VoID file availability check for DailyMed took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for DailyMed took 0.3110935688018799s
Reputation | Calculation of the PageRank for DailyMed took 0.02046799659729004s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00010013580322265625s
Believability | Calculation of trust value for DailyMed took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-dailymed took 6.051151990890503s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7629880905151367s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2844879627227783s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.797645568847656e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.6695637702941895s
Availability | SPARQL endpoint availability check for Diseasome took 0.762096643447876s
Availability | VoID file availability check for Diseasome took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2860982418060303s
Reputation | Calculation of the PageRank for Diseasome took 0.02177143096923828s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011706352233886719s
Believability | Calculation of trust value for Diseasome took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-diseasome took 6.000582933425903s
Availability | SPARQL endpoint availability check for DrugBank took 0.7634580135345459s
Availability | VoID file availability check for DrugBank took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2880513668060303s
Reputation | Calculation of the PageRank for DrugBank took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011396408081054688s
Believability | Calculation of trust value for DrugBank took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.961044073104858s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7632622718811035s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.29228663444519043s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.0205078125s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.3855438232421875e-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.756518125534058s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7722165584564209s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.28464388847351074s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02149176597595215s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0008199214935302734s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 8.0108642578125e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.700684309005737s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.7635304927825928s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2760508060455322s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02027750015258789s
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.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.200241088867188e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-eures took 4.743412971496582s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.779656171798706s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2896571159362793s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.560585021972656e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.439703702926636s
Availability | SPARQL endpoint availability check for MediCare took 0.7719547748565674s
Availability | VoID file availability check for MediCare took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for MediCare took 0.28734397888183594s
Reputation | Calculation of the PageRank for MediCare took 0.021357297897338867s
Interlinking | Calculation of Degree of Connection for MediCare took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.5299530029296875e-05s
Believability | Calculation of trust value for MediCare took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-medicare took 5.435170888900757s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7639462947845459s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.29518699645996094s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.02028679847717285s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.43865966796875e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 8.344650268554688e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.739547491073608s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7647008895874023s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.302929162979126s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.369850158691406e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-sider took 5.463330507278442s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.787825345993042s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.28217601776123047s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.653236389160156e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.7543885707855225s
Availability | SPARQL endpoint availability check for fvdb took 4.3392181396484375e-05s
Availability | VoID file availability check for fvdb took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for fvdb took 0.2908821105957031s
Reputation | Calculation of the PageRank for fvdb took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for fvdb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.9325485229492188e-05s
Believability | Calculation of trust value for fvdb took 6.9141387939453125e-06s
INFO | --- Analysis for fv took 12.602377653121948s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.3392181396484375e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.30429840087890625s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0008699893951416016s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.504753112792969e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.2636184692382812e-05s
INFO | --- Analysis for GACS took 3.363589286804199s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 6.413459777832031e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.292724609375s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.0994415283203125e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 7.62939453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 3.1636104583740234s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.6253204345703125e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.30304551124572754s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0009109973907470703s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.4345855712890625e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 7.3909759521484375e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.1778481006622314s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.363059997558594e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.28542447090148926s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020160675048828125s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.822845458984375e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for garnicaplywood took 3.2916977405548096s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.797645568847656e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.2869141101837158s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02108597755432129s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0009915828704833984s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00011515617370605469s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.152557373046875e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.839860677719116s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.44439125061035156s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.28931689262390137s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.298324584960938e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for gemet took 5.71447491645813s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.4345855712890625e-05s
Availability | VoID file availability check for gemet-annotated took 0.0012853145599365234s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.30422019958496094s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.886222839355469e-05s
Believability | Calculation of trust value for gemet-annotated took 7.62939453125e-06s
INFO | --- Analysis for gemet-annotated took 3.215789556503296s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 1.0299127101898193s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2838890552520752s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 6.9141387939453125e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.641065359115601s
Availability | SPARQL endpoint availability check for Super Ontology took 2.203235149383545s
Availability | VoID file availability check for Super Ontology took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.28058433532714844s
Reputation | Calculation of the PageRank for Super Ontology took 0.020743131637573242s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Super Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 5.1773293018341064s
Availability | SPARQL endpoint availability check for geo.place took 4.172325134277344e-05s
Availability | VoID file availability check for geo.place took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for geo.place took 0.2744288444519043s
Reputation | Calculation of the PageRank for geo.place took 0.020595550537109375s
Interlinking | Calculation of Degree of Connection for geo.place took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.361701965332031e-05s
Believability | Calculation of trust value for geo.place took 6.9141387939453125e-06s
INFO | --- Analysis for geo_place took 3.1013875007629395s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.38690185546875e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.28493452072143555s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020727157592773438s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.0279159545898438e-05s
Believability | Calculation of trust value for Geographic detector model took 6.67572021484375e-06s
INFO | --- Analysis for GeoDetector took 13.060824394226074s
Availability | SPARQL endpoint availability check for geodomainwn took 4.363059997558594e-05s
Availability | VoID file availability check for geodomainwn took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.2864227294921875s
Reputation | Calculation of the PageRank for geodomainwn took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.4836273193359375e-05s
Believability | Calculation of trust value for geodomainwn took 7.867813110351562e-06s
INFO | --- Analysis for geodomainwn took 6.888798952102661s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.291534423828125e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2837259769439697s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.009506225585938e-05s
Believability | Calculation of trust value for GeoEcuador took 8.344650268554688e-06s
INFO | --- Analysis for geoecuador took 13.244309425354004s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.1750123500823975s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007865428924560547s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.2842893600463867s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.987022399902344e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 7.3909759521484375e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.736759185791016s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.4345855712890625e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.27199411392211914s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.2901763916015625e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 6.198883056640625e-06s
INFO | --- Analysis for geographic-openuplabs took 3.1031486988067627s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5539565086364746s
Availability | VoID file availability check for GeoLinkedData took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.30187439918518066s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.606910705566406e-05s
Believability | Calculation of trust value for GeoLinkedData took 5.4836273193359375e-06s
INFO | --- Analysis for geolinkeddata took 4.263997554779053s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.9707679748535156s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.3644413948059082s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02008223533630371s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 7.939338684082031e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 7.0334296226501465s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.506111145019531e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2860908508300781s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00046539306640625s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.3909759521484375e-06s
INFO | --- Analysis for geonames-semantic-web took 3.5138931274414062s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.3392181396484375e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.28576111793518066s
Reputation | Calculation of the PageRank for Geospatial World  took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010418891906738281s
Believability | Calculation of trust value for Geospatial World  took 7.3909759521484375e-06s
INFO | --- Analysis for geospatialworld-net took 3.125234365463257s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.6103551387786865s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.2849006652832031s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013399124145507812s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for geospecies took 6.170362234115601s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.363059997558594e-05s
Availability | VoID file availability check for GeoWordNet took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.29314756393432617s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.792213439941406e-05s
Believability | Calculation of trust value for GeoWordNet took 6.4373016357421875e-06s
INFO | --- Analysis for geowordnet took 7.698337554931641s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.10244917869567871s
Availability | VoID file availability check for German labor law thesaurus took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.28212404251098633s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.796287536621094e-05s
Believability | Calculation of trust value for German labor law thesaurus took 5.9604644775390625e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.6935718059539795s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.7206878662109375e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.2847118377685547s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 3.790855407714844e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 6.389617919921875e-05s
INFO | --- Analysis for germlex took 3.00724196434021s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.6228141784667969s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2834906578063965s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020233154296875s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.487701416015625e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 6.67572021484375e-06s
INFO | --- Analysis for gesis-thesoz took 6.368877649307251s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.728726387023926s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0008263587951660156s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.28452205657958984s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.534027099609375e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for getty-aat took 24.895421981811523s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 2.6445412635803223s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.28673553466796875s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.1021575927734375e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 5.9604644775390625e-06s
INFO | --- Analysis for getty-tgn took 23.808080196380615s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.31244754791259766s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.28558850288391113s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.0517578125e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.4836273193359375e-06s
INFO | --- Analysis for gipuzkoademografia took 3.019460678100586s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.4345855712890625e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.27289414405822754s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 2.9087066650390625e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 6.67572021484375e-06s
INFO | --- Analysis for glastonbury-2011 took 6.2385430335998535s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.2438507080078125e-05s
Availability | VoID file availability check for Global Change Information System took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.28354597091674805s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 2.8848648071289062e-05s
Believability | Calculation of trust value for Global Change Information System took 6.9141387939453125e-06s
INFO | --- Analysis for global-change-information-system took 3.1130025386810303s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.38690185546875e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.28174614906311035s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.363059997558594e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.67572021484375e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.2193753719329834s
Availability | SPARQL endpoint availability check for Glottolog took 4.3392181396484375e-05s
Availability | VoID file availability check for Glottolog took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2922804355621338s
Reputation | Calculation of the PageRank for Glottolog took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Glottolog took 4.649162292480469e-05s
Believability | Calculation of trust value for Glottolog took 6.9141387939453125e-06s
INFO | --- Analysis for glottolog took 7.4938483238220215s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.291534423828125e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.28888845443725586s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00011157989501953125s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 6.9141387939453125e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 5.23932957649231s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.267692565917969e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.2736215591430664s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.86102294921875e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 6.67572021484375e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 3.117497205734253s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.100799560546875e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.27308225631713867s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 2.86102294921875e-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.1486167907714844s
Availability | SPARQL endpoint availability check for 1121 took 4.315376281738281e-05s
Availability | VoID file availability check for 1121 took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for 1121 took 0.28222107887268066s
Reputation | Calculation of the PageRank for 1121 took 0.020072221755981445s
Interlinking | Calculation of Degree of Connection for 1121 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 1121 took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for 1121 took 2.7894973754882812e-05s
Believability | Calculation of trust value for 1121 took 6.9141387939453125e-06s
INFO | --- Analysis for God_ took 3.645636796951294s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.3392181396484375e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2861196994781494s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.125999450683594e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 6.9141387939453125e-06s
INFO | --- Analysis for gold took 4.667423248291016s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.410743713378906e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.27602314949035645s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.67572021484375e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 8.106231689453125e-06s
INFO | --- Analysis for googleart-wrapper took 2.9305198192596436s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.10503101348876953s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.28683924674987793s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.2901763916015625e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 6.9141387939453125e-06s
INFO | --- Analysis for govagribus-denmark took 34.84800434112549s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.398942708969116s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.3013734817504883s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.0108642578125e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.08778214454651s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.6729803085327148s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2883315086364746s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.416175842285156e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 4.5299530029296875e-06s
INFO | --- Analysis for govtrack took 10.461023569107056s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.291534423828125e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.28678178787231445s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.699562072753906e-05s
Believability | Calculation of trust value for greek-administrative-geography took 6.9141387939453125e-06s
INFO | --- Analysis for greek-administrative-geography took 2.6905603408813477s
Availability | SPARQL endpoint availability check for Greek Wordnet took 2.369093179702759s
Availability | VoID file availability check for Greek Wordnet took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.3015096187591553s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 3.743171691894531e-05s
Believability | Calculation of trust value for Greek Wordnet took 6.9141387939453125e-06s
INFO | --- Analysis for greek-wordnet took 4.993895769119263s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 4.95670223236084s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.29396915435791016s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.1444091796875e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 6.198883056640625e-06s
INFO | --- Analysis for greek_prisons_releases took 9.304315567016602s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.8832027912139893s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.27630615234375s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02008342742919922s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.43865966796875e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.152557373046875e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.81989312171936s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 6.031990051269531e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.001264810562133789s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.28783321380615234s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.918212890625e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 4.874783515930176s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 2.2641634941101074s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.001073598861694336s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.28729820251464844s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.4345855712890625e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 7.62939453125e-06s
INFO | --- Analysis for grrp took 4.945110082626343s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.5353012084960938s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2861623764038086s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02016305923461914s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.747245788574219e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for grrt took 4.209703207015991s
Availability | SPARQL endpoint availability check for Geological Timescale took 3.0586583614349365s
Availability | VoID file availability check for Geological Timescale took 0.0006084442138671875s
Extra | Recovery of all triples for Geological Timescale took 2.502676010131836s
Performance | Total latancy measurement for Geological Timescale took 3.182281732559204s
Amount of data | Number of triples check for Geological Timescale took 0.4549260139465332s
Interoperability | New terms check for Geological Timescale took 1.5595757961273193s
Versatility | Languages check for Geological Timescale took 0.5024032592773438s
Interpretability | Number of blank nodes check for Geological Timescale took 0.9648129940032959s
Security | Check HTTPS for Geological Timescale took 0.3701949119567871s
Interpretability | RDF structures check for Geological Timescale took 0.36355042457580566s
Versatility | Serialization formats check for Geological Timescale took 0.4454200267791748s
Availability | RDF dump link check for Geological Timescale took 1.1811158657073975s
License | MR license check for Geological Timescale took 1.0043063163757324s
License | HR license check for Geological Timescale took 0.4879798889160156s
Amount of data | Number of property check for Geological Timescale took 0.3601264953613281s
Understandability | Number of label check for Geological Timescale took 0.41294193267822266s
Understandability | URI regex check for Geological Timescale took 0.736212968826294s
Understandability | Vocabs check for Geological Timescale took 1.0026302337646484s
Verifiability | Authors check for Geological Timescale took 0.9671001434326172s
Verifiability | Publishers check for Geological Timescale took 0.3910083770751953s
Performance | Throughput check for Geological Timescale took 13.363476276397705s
Amount of data | Check the number of entities for Geological Timescale took 0.022460222244262695s
Verifiability | Contribs. check for Geological Timescale took 0.3772294521331787s
Interlinking | sameAs chians check for Geological Timescale took 0.9314789772033691s
Interlinking | skos check for Geological Timescale took 0.4024019241333008s
Interlinking | skos check for Geological Timescale took 0.37605977058410645s
Timeliness | dataset update frequency check for Geological Timescale took 0.8629930019378662s
Currency | Creation date check for Geological Timescale took 0.819127082824707s
Currency | Modification date check for Geological Timescale took 0.9919202327728271s
Rep.Conc. | URIs length for Geological Timescale took 1.5482919216156006s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.3842923641204834s
Accuracy | Check Functional Property for Geological Timescale took 0.39382386207580566s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.3835580348968506s
Accuracy | Check Empty annotation labels for Geological Timescale took 0.7444417476654053s
Accuracy | Check White space in annotation for Geological Timescale took 0.015689373016357422s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07467293739318848s
Consistency | Disjoint class check for Geological Timescale took 0.39627695083618164s
Consistency | Check Misplaced properties for Geological Timescale took 1.4550929069519043s
Consistency | Misplaced classes for Geological Timescale took 1.098557949066162s
Consistency | Check Ontology hijacking for Geological Timescale took 2.1638596057891846s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1480376720428467s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 1.5870144367218018s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05095171928405762s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.972435712814331s
Security | Sign check for Geological Timescale took 0.3934950828552246s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.8532145023345947s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.3968329429626465s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020131349563598633s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 8.7738037109375e-05s
Believability | Calculation of trust value for Geological Timescale took 6.9141387939453125e-06s
INFO | --- Analysis for GTS took 94.01810693740845s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2852325439453125s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 6.198883056640625e-06s
INFO | --- Analysis for GTS-ont took 3.3004302978515625s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.220008850097656e-05s
Availability | VoID file availability check for GUTSTOK  took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.30065178871154785s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.9087066650390625e-05s
Believability | Calculation of trust value for GUTSTOK  took 5.9604644775390625e-06s
INFO | --- Analysis for Guillaume_Forget took 2.5448782444000244s
Availability | SPARQL endpoint availability check for Project Gutenberg took 5.745887756347656e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.30365586280822754s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.67572021484375e-05s
Believability | Calculation of trust value for Project Gutenberg took 7.867813110351562e-06s
INFO | --- Analysis for gutenberg took 10.116274118423462s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.315376281738281e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.28934192657470703s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020467519760131836s
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.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.552436828613281e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 8.344650268554688e-06s
INFO | --- Analysis for gwa-ili took 5.326706647872925s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.363059997558594e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.3017563819885254s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02073359489440918s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.075599670410156e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 5.4836273193359375e-06s
INFO | --- Analysis for GWR took 14.380789041519165s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.1961669921875e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.3046743869781494s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020774364471435547s
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.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 2.9802322387695312e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 6.198883056640625e-06s
INFO | --- Analysis for HASM took 9.849174737930298s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.0531158447265625e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.28708362579345703s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.0279159545898438e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 5.245208740234375e-06s
INFO | --- Analysis for hcls-knowledge-base took 3.122030258178711s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 2.8167788982391357s
Availability | VoID file availability check for HealthCare Ontology took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.30532145500183105s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.504753112792969e-05s
Believability | Calculation of trust value for HealthCare Ontology took 5.7220458984375e-06s
INFO | --- Analysis for HealthCare_Ontology took 5.8691771030426025s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.482269287109375e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.28197669982910156s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 7.748603820800781e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 8.106231689453125e-06s
INFO | --- Analysis for heartfailure took 3.419807195663452s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.97722887992859s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007603168487548828s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.2873694896697998s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.2438507080078125e-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 122.26894974708557s
Availability | SPARQL endpoint availability check for Hedatuz took 0.28639650344848633s
Availability | VoID file availability check for Hedatuz took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.28046727180480957s
Reputation | Calculation of the PageRank for Hedatuz took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.863739013671875e-05s
Believability | Calculation of trust value for Hedatuz took 7.867813110351562e-06s
INFO | --- Analysis for hedatuz took 3.7494559288024902s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.1270134449005127s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.28116703033447266s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012755393981933594s
Believability | Calculation of trust value for Hellenic Fire Brigade took 5.7220458984375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.736783742904663s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.02032947540283203s
Availability | VoID file availability check for Hellenic Police took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.28931355476379395s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001289844512939453s
Believability | Calculation of trust value for Hellenic Police took 5.7220458984375e-06s
INFO | --- Analysis for hellenic-police took 2.6969051361083984s
Availability | SPARQL endpoint availability check for Hermos took 4.3392181396484375e-05s
Availability | VoID file availability check for Hermos took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Hermos took 0.28552699089050293s
Reputation | Calculation of the PageRank for Hermos took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hermos took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.075599670410156e-05s
Believability | Calculation of trust value for Hermos took 7.867813110351562e-06s
INFO | --- Analysis for Hermos took 3.2034573554992676s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.649162292480469e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2840852737426758s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020202159881591797s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.8133392333984375e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 7.152557373046875e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.6239895820617676s
Availability | SPARQL endpoint availability check for HITO took 0.4968907833099365s
Availability | VoID file availability check for HITO took 0.0006532669067382812s
Extra | Recovery of all triples for HITO took 3.367435932159424s
Performance | Total latancy measurement for HITO took 1.0266053676605225s
Amount of data | Number of triples check for HITO took 0.20893502235412598s
Interoperability | New terms check for HITO took 1.3884246349334717s
Versatility | Languages check for HITO took 0.22213530540466309s
Interpretability | Number of blank nodes check for HITO took 0.2052021026611328s
Interpretability | RDF structures check for HITO took 0.2189483642578125s
Versatility | Serialization formats check for HITO took 0.20876359939575195s
Availability | RDF dump link check for HITO took 0.20723938941955566s
License | MR license check for HITO took 0.21112751960754395s
License | HR license check for HITO took 0.23384857177734375s
Amount of data | Number of property check for HITO took 0.20682144165039062s
Understandability | Number of label check for HITO took 0.21881461143493652s
Understandability | URI regex check for HITO took 0.4106438159942627s
Understandability | Vocabs check for HITO took 0.20788025856018066s
Verifiability | Authors check for HITO took 0.21012330055236816s
Verifiability | Publishers check for HITO took 0.21071815490722656s
Performance | Throughput check for HITO took 10.283041000366211s
Amount of data | Check the number of entities for HITO took 0.00011539459228515625s
Verifiability | Contribs. check for HITO took 0.20780563354492188s
Interlinking | sameAs chians check for HITO took 0.20450544357299805s
Interlinking | skos check for HITO took 0.21755409240722656s
Interlinking | skos check for HITO took 0.20504093170166016s
Timeliness | dataset update frequency check for HITO took 0.21152353286743164s
Currency | Creation date check for HITO took 0.41709089279174805s
Currency | Modification date check for HITO took 0.4267292022705078s
Rep.Conc. | URIs length for HITO took 1.2715585231781006s
Interoperability | New vocabularies check for HITO took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.20438408851623535s
Accuracy | Check Functional Property for HITO took 0.2054910659790039s
Accuracy | Check Inverse Functional Property for HITO took 0.20851874351501465s
Accuracy | Check Empty annotation labels for HITO took 0.5819306373596191s
Accuracy | Check White space in annotation for HITO took 0.0135345458984375s
Accuracy | Check Datatype consistency for HITO took 0.06928634643554688s
Consistency | Disjoint class check for HITO took 0.20448827743530273s
Consistency | Check Misplaced properties for HITO took 0.5469815731048584s
Consistency | Misplaced classes for HITO took 0.3747365474700928s
Consistency | Check Ontology hijacking for HITO took 1.6409709453582764s
Consistency | Check Invalid usage of undefined classes for HITO took 1.1479451656341553s
Consistency | Check Invalid usage of undefined properties for HITO took 1.422513484954834s
Conciseness | Check Extensional conciseness for HITO took 0.05971646308898926s
Conciseness | Check Intensional conciseness for HITO took 0.20517754554748535s
Security | Sign check for HITO took 0.2047412395477295s
Availability | Check URIs Dereferenciability for HITO took 1595.6089646816254s
Completeness | Calculation of interlinking completeness for HITO took 1.6160752773284912s
Reputation | Calculation of the PageRank for HITO took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for HITO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HITO took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for HITO took 9.322166442871094e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.430511474609375e-06s
Believability | Calculation of trust value for HITO took 1.2159347534179688e-05s
INFO | --- Analysis for hito took 1649.8534100055695s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 7.258931636810303s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.290956974029541s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02092885971069336s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 2.8848648071289062e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 7.3909759521484375e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 33.28928804397583s
Availability | SPARQL endpoint availability check for Homologene took 5.340576171875e-05s
Availability | VoID file availability check for Homologene took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Homologene took 0.2852914333343506s
Reputation | Calculation of the PageRank for Homologene took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Homologene took 2.9802322387695312e-05s
Believability | Calculation of trust value for Homologene took 7.152557373046875e-06s
INFO | --- Analysis for homologene took 4.50335693359375s
Availability | SPARQL endpoint availability check for gseg took 4.839897155761719e-05s
Availability | VoID file availability check for gseg took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for gseg took 0.28675174713134766s
Reputation | Calculation of the PageRank for gseg took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for gseg took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for gseg took 2.8133392333984375e-05s
Believability | Calculation of trust value for gseg took 6.9141387939453125e-06s
INFO | --- Analysis for hongse took 4.151731967926025s
Availability | SPARQL endpoint availability check for Noticias Universia took 6.842613220214844e-05s
Availability | VoID file availability check for Noticias Universia took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.28484082221984863s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 2.8371810913085938e-05s
Believability | Calculation of trust value for Noticias Universia took 6.9141387939453125e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 3.141650915145874s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 6.67572021484375e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2851276397705078s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020241737365722656s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007350444793701172s
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 6.9141387939453125e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 3.1010258197784424s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 2.037992238998413s
Availability | VoID file availability check for COURAGE Dataset took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.28362035751342773s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 5.828949213027954s
Availability | SPARQL endpoint availability check for RoadTrb took 4.363059997558594e-05s
Availability | VoID file availability check for RoadTrb took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2846035957336426s
Reputation | Calculation of the PageRank for RoadTrb took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.0279159545898438e-05s
Believability | Calculation of trust value for RoadTrb took 6.9141387939453125e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.616502523422241s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.30710816383361816s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020406484603881836s
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.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.9087066650390625e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 24.735734939575195s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.291534423828125e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2690753936767578s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.9325485229492188e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 7.152557373046875e-06s
INFO | --- Analysis for http:pakistan.com took 2.551656723022461s
Availability | SPARQL endpoint availability check for CEDICT took 4.363059997558594e-05s
Availability | VoID file availability check for CEDICT took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for CEDICT took 0.2862820625305176s
Reputation | Calculation of the PageRank for CEDICT took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for CEDICT took 2.9325485229492188e-05s
Believability | Calculation of trust value for CEDICT took 7.152557373046875e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.776867628097534s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.787853956222534s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.28685569763183594s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0008027553558349609s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.152557373046875e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.4373016357421875e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 10.27126407623291s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.076957702636719e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.27501797676086426s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 2.765655517578125e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 3.1556026935577393s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.267692565917969e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.28380274772644043s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.0040740966796875e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 8.344650268554688e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.5347540378570557s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for Soccer Dataset took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.28757596015930176s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.170967102050781e-05s
Believability | Calculation of trust value for Soccer Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.msm.com took 2.547093391418457s
Availability | SPARQL endpoint availability check for Game Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Game Ontology took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.2836732864379883s
Reputation | Calculation of the PageRank for Game Ontology took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for Game Ontology took 6.67572021484375e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.0875871181488037s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0004646778106689453s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2787330150604248s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020240306854248047s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 2.7179718017578125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.152557373046875e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.3669145107269287s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.1961669921875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.000244140625s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.272946834564209s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02024054527282715s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.7894973754882812e-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.5003373622894287s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.2438507080078125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.27300286293029785s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020203113555908203s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8133392333984375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.4811527729034424s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.225440979003906e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00036144256591796875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26962780952453613s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7418136596679688e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.4373016357421875e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.5193259716033936s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.792213439941406e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.28440260887145996s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8371810913085938e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1444091796875e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.5590906143188477s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.8160552978515625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.28325581550598145s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02020430564880371s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9087066650390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.601926326751709s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.315376281738281e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.28856468200683594s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7418136596679688e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.518418550491333s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.38690185546875e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.2917637825012207s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020155906677246094s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.218650817871094e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 6.9141387939453125e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.1152663230896s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.2257871627807617s
Availability | VoID file availability check for Bookkeeping took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.28659987449645996s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bookkeeping took 6.9141387939453125e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.316090106964111s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Legal Ontology took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.29277658462524414s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.504753112792969e-05s
Believability | Calculation of trust value for Legal Ontology took 8.58306884765625e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 3.163865566253662s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.601478576660156e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0011818408966064453s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.28473949432373047s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.0209805965423584s
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.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.082389831542969e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 8.106231689453125e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.86494779586792s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.363059997558594e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.28375720977783203s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.0517578125e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 8.106231689453125e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.794217824935913s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 6.604194641113281e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.28948497772216797s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.170967102050781e-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.1371476650238037s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 5.173683166503906e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2819647789001465s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.021402359008789062s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 7.62939453125e-06s
INFO | --- Analysis for hud-library-usagedata took 3.1378250122070312s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.6224708557128906s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.30083680152893066s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010728836059570312s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 6.67572021484375e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.624150991439819s
Availability | SPARQL endpoint availability check for IATE RDF took 4.5299530029296875e-05s
Availability | VoID file availability check for IATE RDF took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.27854180335998535s
Reputation | Calculation of the PageRank for IATE RDF took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.695487976074219e-05s
Believability | Calculation of trust value for IATE RDF took 8.58306884765625e-06s
INFO | --- Analysis for iate-rdf took 2.6480748653411865s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 0.6927661895751953s
Availability | VoID file availability check for IATI as Linked Data took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2899911403656006s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020551681518554688s
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.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.463859558105469e-05s
Believability | Calculation of trust value for IATI as Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for iati-as-linked-data took 7.759249687194824s
Availability | SPARQL endpoint availability check for ICANE took 0.3469886779785156s
Availability | VoID file availability check for ICANE took 0.0008168220520019531s
Completeness | Calculation of interlinking completeness for ICANE took 0.28423309326171875s
Reputation | Calculation of the PageRank for ICANE took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for ICANE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for ICANE took 9.751319885253906e-05s
Believability | Calculation of trust value for ICANE took 4.5299530029296875e-06s
INFO | --- Analysis for icane took 3.749842405319214s
Availability | SPARQL endpoint availability check for ichoose took 0.164564847946167s
Availability | VoID file availability check for ichoose took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for ichoose took 0.2870445251464844s
Reputation | Calculation of the PageRank for ichoose took 0.0207366943359375s
Interlinking | Calculation of Degree of Connection for ichoose took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.985664367675781e-05s
Believability | Calculation of trust value for ichoose took 1.239776611328125e-05s
INFO | --- Analysis for ichoose took 42.09581780433655s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.7637391090393066s
Availability | VoID file availability check for The Iconology Dataset took 0.0006134510040283203s
Extra | Recovery of all triples for The Iconology Dataset took 4.819089651107788s
Performance | Total latancy measurement for The Iconology Dataset took 0.4410431385040283s
Amount of data | Number of triples check for The Iconology Dataset took 0.2066500186920166s
Interoperability | New terms check for The Iconology Dataset took 1.3113112449645996s
Versatility | Languages check for The Iconology Dataset took 0.5733702182769775s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.2260282039642334s
Interpretability | RDF structures check for The Iconology Dataset took 0.10590767860412598s
Versatility | Serialization formats check for The Iconology Dataset took 0.09962320327758789s
Availability | RDF dump link check for The Iconology Dataset took 0.0865330696105957s
License | MR license check for The Iconology Dataset took 0.0963752269744873s
License | HR license check for The Iconology Dataset took 0.3222064971923828s
Amount of data | Number of property check for The Iconology Dataset took 0.11270451545715332s
Understandability | Number of label check for The Iconology Dataset took 0.1410388946533203s
Understandability | URI regex check for The Iconology Dataset took 0.16528105735778809s
Understandability | Vocabs check for The Iconology Dataset took 0.08622503280639648s
Verifiability | Authors check for The Iconology Dataset took 0.09938764572143555s
Verifiability | Publishers check for The Iconology Dataset took 0.08781623840332031s
Performance | Throughput check for The Iconology Dataset took 10.451310873031616s
Amount of data | Check the number of entities for The Iconology Dataset took 0.0005555152893066406s
Verifiability | Contribs. check for The Iconology Dataset took 0.08776259422302246s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09253692626953125s
Interlinking | skos check for The Iconology Dataset took 0.08897829055786133s
Interlinking | skos check for The Iconology Dataset took 0.10318946838378906s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08996105194091797s
Currency | Creation date check for The Iconology Dataset took 0.18053150177001953s
Currency | Modification date check for The Iconology Dataset took 0.18667173385620117s
Rep.Conc. | URIs length for The Iconology Dataset took 1.3602945804595947s
Interoperability | New vocabularies check for The Iconology Dataset took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08148574829101562s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.2660644054412842s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.0162351131439209s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.43705177307128906s
Consistency | Disjoint class check for The Iconology Dataset took 0.09824705123901367s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15708470344543457s
Consistency | Misplaced classes for The Iconology Dataset took 0.8919477462768555s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.5734977722167969s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.1894729137420654s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.2678582668304443s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.30210256576538086s
Security | Sign check for The Iconology Dataset took 0.08459115028381348s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2621.570556163788s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.0402758121490479s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.02104473114013672s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.9788742065429688e-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.106231689453125e-06s
INFO | --- Analysis for iconology-dataset took 2681.807839870453s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.410743713378906e-05s
Availability | VoID file availability check for Identifiers.org took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.7261073589324951s
Reputation | Calculation of the PageRank for Identifiers.org took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 5.221366882324219e-05s
Believability | Calculation of trust value for Identifiers.org took 8.106231689453125e-06s
INFO | --- Analysis for identifiers-org took 4.494067907333374s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.363059997558594e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2845637798309326s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 8.058547973632812e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 9.059906005859375e-06s
INFO | --- Analysis for idreffr took 4.276300668716431s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 1.0841786861419678s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.28528380393981934s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.863739013671875e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 7.3909759521484375e-06s
INFO | --- Analysis for ids took 5.071537733078003s
Availability | SPARQL endpoint availability check for ietflang took 4.5299530029296875e-05s
Availability | VoID file availability check for ietflang took 0.0007977485656738281s
Completeness | Calculation of interlinking completeness for ietflang took 0.2925758361816406s
Reputation | Calculation of the PageRank for ietflang took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for ietflang took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.744529724121094e-05s
Believability | Calculation of trust value for ietflang took 6.4373016357421875e-06s
INFO | --- Analysis for ietflang took 14.141294002532959s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.5358281135559082s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.2999086380004883s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for IGVLL took 4.187147378921509s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.5007133483886719s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0007557868957519531s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.9464352130889893s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 1.0332558155059814s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.21192693710327148s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.409484624862671s
Versatility | Languages check for 3LGM² IHE Ontology took 0.2094440460205078s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.20362567901611328s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.20593643188476562s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.20401644706726074s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.20529937744140625s
License | MR license check for 3LGM² IHE Ontology took 0.20509886741638184s
License | HR license check for 3LGM² IHE Ontology took 0.21680283546447754s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.2044520378112793s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.2050623893737793s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.41637516021728516s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.2072610855102539s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.20664405822753906s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.20227479934692383s
Performance | Throughput check for 3LGM² IHE Ontology took 10.262616157531738s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 0.000110626220703125s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.20814085006713867s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.20824027061462402s
Interlinking | skos check for 3LGM² IHE Ontology took 0.2076270580291748s
Interlinking | skos check for 3LGM² IHE Ontology took 0.2084352970123291s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.20659708976745605s
Currency | Creation date check for 3LGM² IHE Ontology took 0.41542935371398926s
Currency | Modification date check for 3LGM² IHE Ontology took 0.4184119701385498s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8866462707519531s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.20850467681884766s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.20328235626220703s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.20252728462219238s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3442726135253906s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.001604318618774414s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05117535591125488s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.20525813102722168s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4734320640563965s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2872352600097656s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.5455338954925537s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.2006933689117432s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.472266435623169s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03279685974121094s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.20726394653320312s
Security | Sign check for 3LGM² IHE Ontology took 0.2060837745666504s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 398.912015914917s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.37177181243896484s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.02410101890563965s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for IHE took 444.28931164741516s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.0859537124633789s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.27062392234802246s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.02050948143005371s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 7.3909759521484375e-06s
INFO | --- Analysis for iislod-test took 3.0859756469726562s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 8.034706115722656e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.28557801246643066s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020195960998535156s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.0994415283203125e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 6.9141387939453125e-06s
INFO | --- Analysis for ILUSOC took 15.79518437385559s
Availability | SPARQL endpoint availability check for im@sparql took 6.694607734680176s
Availability | VoID file availability check for im@sparql took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for im@sparql took 0.30149292945861816s
Reputation | Calculation of the PageRank for im@sparql took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.0040740966796875e-05s
Believability | Calculation of trust value for im@sparql took 1.1920928955078125e-05s
INFO | --- Analysis for im@sparql took 13.760101795196533s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.3392181396484375e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.28400278091430664s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.075599670410156e-05s
Believability | Calculation of trust value for imagery bailingniao took 6.4373016357421875e-06s
INFO | --- Analysis for imagery_bailingniao took 3.7242023944854736s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1401407718658447s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006144046783447266s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 25.834203243255615s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.3809096813201904s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.019362211227417s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.459139823913574s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.71297812461853s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 7.559158802032471s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.688441276550293s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7392256259918213s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7650957107543945s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7146670818328857s
License | MR license check for Imagesnippets Image Descriptions took 0.7217466831207275s
License | HR license check for Imagesnippets Image Descriptions took 10.696851015090942s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7299320697784424s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.830629825592041s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4398581981658936s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.705899715423584s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.6633045673370361s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7111563682556152s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.402948379516602s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 6.103515625e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7155122756958008s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7039647102355957s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6810972690582275s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.692763090133667s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.710655927658081s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.4372937679290771s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4136326313018799s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 29.789628744125366s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.723832368850708s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7386958599090576s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7027406692504883s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7305662631988525s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.896585941314697s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 15.047041654586792s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.486949443817139s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00015211105346679688s
Security | Sign check for Imagesnippets Image Descriptions took 0.7331798076629639s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.3979966640472412s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.430511474609375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 7.152557373046875e-06s
INFO | --- Analysis for imagesnippets took 260.73866057395935s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 1.0247929096221924s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0003635883331298828s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.3310277462005615s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.893013000488281e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for imf-linked-data took 4.621675729751587s
Availability | SPARQL endpoint availability check for IMGpedia took 4.1484832763671875e-05s
Availability | VoID file availability check for IMGpedia took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.28785157203674316s
Reputation | Calculation of the PageRank for IMGpedia took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for IMGpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.075599670410156e-05s
Believability | Calculation of trust value for IMGpedia took 7.62939453125e-06s
INFO | --- Analysis for imgpedia took 3.6144888401031494s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.315376281738281e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.28428053855895996s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 3.1948089599609375e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 6.9141387939453125e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 3.1456499099731445s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.410743713378906e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.28345799446105957s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.0728836059570312e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 7.867813110351562e-06s
INFO | --- Analysis for Imtiaz took 2.511554718017578s
Availability | SPARQL endpoint availability check for Royalty Free Music took 5.1021575927734375e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.28301143646240234s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020272493362426758s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.0517578125e-05s
Believability | Calculation of trust value for Royalty Free Music took 7.3909759521484375e-06s
INFO | --- Analysis for inaudio.org took 3.9812164306640625s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.1484832763671875e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.3015785217285156s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 2.8133392333984375e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 6.9141387939453125e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 3.187511444091797s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.1484832763671875e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.2885119915008545s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.02030014991760254s
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.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 2.7894973754882812e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 7.152557373046875e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 3.0909602642059326s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.47417712211608887s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.28696465492248535s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0009031295776367188s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 4.291534423828125e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 4.236055135726929s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 5.6743621826171875e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.287381649017334s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.02049994468688965s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.0994415283203125e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 7.3909759521484375e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 3.1246747970581055s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.267692565917969e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2701694965362549s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00011467933654785156s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 7.3909759521484375e-06s
INFO | --- Analysis for ineverycrea took 18.311952114105225s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.38690185546875e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.289837121963501s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020310163497924805s
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.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.036064147949219e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 6.9141387939453125e-06s
INFO | --- Analysis for ineverycrea-argentina took 11.976905584335327s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 524.4165620803833s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.2903444766998291s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.772445678710938e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.152557373046875e-06s
INFO | --- Analysis for influence-tracker-dataset took 1081.6953892707825s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.315376281738281e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.2732069492340088s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.886222839355469e-05s
Believability | Calculation of trust value for INSEMTIVES took 7.3909759521484375e-06s
INFO | --- Analysis for insemtives took 5.07045316696167s
Availability | SPARQL endpoint availability check for instagram.person took 4.076957702636719e-05s
Availability | VoID file availability check for instagram.person took 0.0003476142883300781s
Completeness | Calculation of interlinking completeness for instagram.person took 0.28381967544555664s
Reputation | Calculation of the PageRank for instagram.person took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for instagram.person took 2.9802322387695312e-05s
Believability | Calculation of trust value for instagram.person took 7.152557373046875e-06s
INFO | --- Analysis for instagram_person took 3.536317825317383s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.220008850097656e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.28980016708374023s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.9802322387695312e-05s
Believability | Calculation of trust value for instagram.videoobject took 1.239776611328125e-05s
INFO | --- Analysis for instagram_videoobject took 3.100980520248413s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2909085750579834s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 2.7894973754882812e-05s
Believability | Calculation of trust value for Instance Hub Countries took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-countries took 4.043936491012573s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.2438507080078125e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.28293609619140625s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.0202791690826416s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.8371810913085938e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 5.7220458984375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.9740264415740967s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.2898590564727783s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 2.86102294921875e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 8.344650268554688e-06s
INFO | --- Analysis for instance-hub-organizations took 3.5772156715393066s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub People took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.33518338203430176s
Reputation | Calculation of the PageRank for Instance Hub People took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub People took 1.2159347534179688e-05s
INFO | --- Analysis for instance-hub-people took 3.1936957836151123s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.649162292480469e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.2929811477661133s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020322084426879883s
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.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 6.4373016357421875e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 3.0840306282043457s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.2998020648956299s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 6.198883056640625e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 3.085491418838501s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2828233242034912s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.02021479606628418s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 2.8133392333984375e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 3.109710931777954s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.3089761734008789s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020298242568969727s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 2.8133392333984375e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-crops took 3.1068572998046875s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.3392181396484375e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.29942798614501953s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 3.1090173721313477s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.1961669921875e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.2802412509918213s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 2.9802322387695312e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 3.031329393386841s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.315376281738281e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.29479336738586426s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 2.7894973754882812e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 3.125746250152588s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.124641418457031e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.27602386474609375s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0009133815765380859s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.2901763916015625e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.3909759521484375e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 3.1150262355804443s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.291534423828125e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0004055500030517578s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.2748401165008545s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020128726959228516s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.441375732421875e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for interactivemaps-gnoss took 8.1888747215271s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.267692565917969e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2604348659515381s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020209312438964844s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 2.86102294921875e-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.0247409343719482s
Availability | SPARQL endpoint availability check for intervalue took 7.632122039794922s
Availability | VoID file availability check for intervalue took 0.0003578662872314453s
Completeness | Calculation of interlinking completeness for intervalue took 0.27289414405822754s
Reputation | Calculation of the PageRank for intervalue took 0.020364999771118164s
Interlinking | Calculation of Degree of Connection for intervalue took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.890296936035156e-05s
Believability | Calculation of trust value for intervalue took 5.9604644775390625e-06s
INFO | --- Analysis for intervalue took 10.188673257827759s
Availability | SPARQL endpoint availability check for Inztrow took 4.8160552978515625e-05s
Availability | VoID file availability check for Inztrow took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2968142032623291s
Reputation | Calculation of the PageRank for Inztrow took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.0279159545898438e-05s
Believability | Calculation of trust value for Inztrow took 7.3909759521484375e-06s
INFO | --- Analysis for Inztrow took 4.990604639053345s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.27289414405822754s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 5.1021575927734375e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 7.152557373046875e-06s
INFO | --- Analysis for ipbes took 3.9181768894195557s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.2438507080078125e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0009837150573730469s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.27147483825683594s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020380735397338867s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.3392181396484375e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 6.4373016357421875e-06s
INFO | --- Analysis for iptc-newscodes took 3.463839530944824s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.4345855712890625e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.3017561435699463s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.170967102050781e-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.0938515663146973s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 1.9676940441131592s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0007901191711425781s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.26973867416381836s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.00010085105895996094s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.152557373046875e-06s
INFO | --- Analysis for iserve took 7.1078479290008545s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.0296413898468s
Availability | VoID file availability check for ISIC V4 took 0.00102996826171875s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2825899124145508s
Reputation | Calculation of the PageRank for ISIC V4 took 0.02108144760131836s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 5.078315734863281e-05s
Believability | Calculation of trust value for ISIC V4 took 5.245208740234375e-06s
INFO | --- Analysis for isic-v4 took 116.06504917144775s
Availability | SPARQL endpoint availability check for Isidore took 4.220008850097656e-05s
Availability | VoID file availability check for Isidore took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Isidore took 0.28273868560791016s
Reputation | Calculation of the PageRank for Isidore took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for Isidore took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.956390380859375e-05s
Believability | Calculation of trust value for Isidore took 6.9141387939453125e-06s
INFO | --- Analysis for isidore took 3.162935256958008s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.291534423828125e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2853693962097168s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020574092864990234s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.104873657226562e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 4.76837158203125e-06s
INFO | --- Analysis for isil-dbpedia took 4.953023910522461s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.28711462020874023s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 6.67572021484375e-06s
INFO | --- Analysis for iso-3166-2-data took 3.14882755279541s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.38690185546875e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.28067731857299805s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020337820053100586s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 5.3882598876953125e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 7.152557373046875e-06s
INFO | --- Analysis for iso-639-oasis took 3.137821912765503s
Availability | SPARQL endpoint availability check for ISOcat took 4.124641418457031e-05s
Availability | VoID file availability check for ISOcat took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for ISOcat took 0.2891514301300049s
Reputation | Calculation of the PageRank for ISOcat took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for ISOcat took 5.91278076171875e-05s
Believability | Calculation of trust value for ISOcat took 7.152557373046875e-06s
INFO | --- Analysis for isocat took 33.46487498283386s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.410743713378906e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.2794029712677002s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.314018249511719e-05s
Believability | Calculation of trust value for ISOcat-metadata took 7.3909759521484375e-06s
INFO | --- Analysis for isocat-metadata took 5.275361776351929s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.267692565917969e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.2811281681060791s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.020700931549072266s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.075599670410156e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-ihi took 3.1202728748321533s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4123711585998535s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0003521442413330078s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.06344223022461s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8728299140930176s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24215912818908691s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.9637577533721924s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 92.72194910049438s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.32399535179138184s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11726593971252441s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1969153881072998s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18022632598876953s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18810057640075684s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2551999092102051s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.87057256698608s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2289431095123291s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4308598041534424s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5698449611663818s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24488234519958496s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2424614429473877s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17186284065246582s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.335728406906128s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.62939453125e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2390880584716797s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2774379253387451s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.46073365211486816s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.49147915840148926s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2464885711669922s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.33687281608581543s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19537353515625s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 15.544803619384766s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18019580841064453s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16575932502746582s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1571485996246338s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.834132671356201s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31076788902282715s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28644251823425293s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15580320358276367s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.79726243019104s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9864580631256104s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.979468822479248s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2071466445922852s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.822726726531982s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.29135942459106445s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2236473560333252s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2020401954650879s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.3021080493927s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8844540119171143s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.775161743164062e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2159347534179688e-05s
INFO | --- Analysis for ispra-lod-place took 484.3413121700287s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.172325134277344e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2889242172241211s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.024655580520629883s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.600120544433594e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-rmn took 4.909258127212524s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.17223310470581055s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0006229877471923828s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 9.511319875717163s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.8498148918151855s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.25139760971069336s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.9537129402160645s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.42085409164429s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.23000359535217285s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.14226818084716797s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.21117615699768066s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.18175530433654785s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.19681715965270996s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.2572669982910156s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 92.1202745437622s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.24425768852233887s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.3892178535461426s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.5604479312896729s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.25560712814331055s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.2531416416168213s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.16983532905578613s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.53451919555664s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.081031799316406e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.24277853965759277s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.27493977546691895s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.484896183013916s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.48891520500183105s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.351104736328125s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3565671443939209s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.17603206634521484s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 15.539814472198486s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.16603755950927734s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.18221139907836914s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.19454240798950195s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 4.771847724914551s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.31416773796081543s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2753129005432129s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.17421913146972656s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.809867143630981s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 1.0060334205627441s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 4.326559543609619s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.2419161796569824s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.903083324432373s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2909104824066162s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.18873810768127441s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.1982877254486084s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.491544961929321s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.39176058769226074s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021184682846069336s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.1961669921875e-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.62939453125e-06s
INFO | --- Analysis for ispra-lod-ron took 466.13128542900085s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.1961669921875e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.295330286026001s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020672082901000977s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.0517578125e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 6.9141387939453125e-06s
INFO | --- Analysis for ispra-lod-sc took 3.6036341190338135s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.7473933696746826s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.28412485122680664s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.02077317237854004s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.703636169433594e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 6.67572021484375e-06s
INFO | --- Analysis for issa-agritrop took 5.075672626495361s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.4345855712890625e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2835421562194824s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.314018249511719e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 6.67572021484375e-06s
INFO | --- Analysis for ISSN:0080-3626 took 3.00700306892395s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.3392181396484375e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2906789779663086s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.0517578125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 5.7220458984375e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 3.0049970149993896s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.291534423828125e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.28748607635498047s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 2.9325485229492188e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 7.152557373046875e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.7565224170684814s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.8216140270233154s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0003635883331298828s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.29413771629333496s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.797645568847656e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.0067901611328125e-06s
INFO | --- Analysis for istat-immigration took 4.387344598770142s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.172325134277344e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.29434895515441895s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.147125244140625e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for istat-immigrazione took 3.185391902923584s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.4044966697692871s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2855551242828369s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.0994415283203125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 4.291534423828125e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.260298490524292s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.7436625957489014s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2655680179595947s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.367134094238281e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 7.3909759521484375e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 4.742735862731934s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.1484832763671875e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.2741208076477051s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 2.8848648071289062e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 1.239776611328125e-05s
INFO | --- Analysis for iucr-acta-cryst-e took 3.09735107421875s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.076957702636719e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.27988386154174805s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0008578300476074219s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.1948089599609375e-05s
Believability | Calculation of trust value for IWMI Research Reports took 7.62939453125e-06s
INFO | --- Analysis for iwmi-research-reports took 3.062551736831665s
Availability | SPARQL endpoint availability check for IWN took 4.220008850097656e-05s
Availability | VoID file availability check for IWN took 0.0003154277801513672s
Completeness | Calculation of interlinking completeness for IWN took 0.29205870628356934s
Reputation | Calculation of the PageRank for IWN took 0.020179033279418945s
Interlinking | Calculation of Degree of Connection for IWN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for IWN took 3.504753112792969e-05s
Believability | Calculation of trust value for IWN took 6.67572021484375e-06s
INFO | --- Analysis for iwn took 5.952532052993774s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.00543212890625e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.3009333610534668s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 2.9802322387695312e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 7.152557373046875e-06s
INFO | --- Analysis for j-global-knowledge took 3.1892905235290527s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.2438507080078125e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.2993957996368408s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.02021932601928711s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.86102294921875e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 7.152557373046875e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 3.1128528118133545s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.237270593643188s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0008981227874755859s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2861359119415283s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 5.936622619628906e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 6.9141387939453125e-06s
INFO | --- Analysis for jamendo-dbtune took 25.46654224395752s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.1961669921875e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2825298309326172s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.57763671875e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.44246506690979s
Availability | SPARQL endpoint availability check for JEL Classification took 8.559226989746094e-05s
Availability | VoID file availability check for JEL Classification took 0.0011401176452636719s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2916250228881836s
Reputation | Calculation of the PageRank for JEL Classification took 0.02025151252746582s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.8133392333984375e-05s
Believability | Calculation of trust value for JEL Classification took 1.2159347534179688e-05s
INFO | --- Analysis for jel-classification took 5.072707176208496s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 0.6470768451690674s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.28888535499572754s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020129919052124023s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 6.198883056640625e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 9.356971025466919s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.6902709007263s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0007355213165283203s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.3172469139099121s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.319450378417969e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 7.3909759521484375e-06s
INFO | --- Analysis for jita took 540.510782957077s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.0531158447265625e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.7609808444976807s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.022589683532714844s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0012006759643554688s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 4.172325134277344e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.62939453125e-06s
INFO | --- Analysis for jmdict took 6.408387184143066s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.08120560646057s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.7413058280944824s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.441375732421875e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.152557373046875e-06s
INFO | --- Analysis for john-goodwins-family-tree took 64.63266611099243s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.291534423828125e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2885446548461914s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020173311233520508s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.147125244140625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 8.106231689453125e-06s
INFO | --- Analysis for jp-cos took 5.584207534790039s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.3392181396484375e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0007684230804443359s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.3030848503112793s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.076957702636719e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 7.3909759521484375e-06s
INFO | --- Analysis for jp-textbook took 4.6075592041015625s
Availability | SPARQL endpoint availability check for JRC-Names took 4.267692565917969e-05s
Availability | VoID file availability check for JRC-Names took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.28452014923095703s
Reputation | Calculation of the PageRank for JRC-Names took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.218650817871094e-05s
Believability | Calculation of trust value for JRC-Names took 6.198883056640625e-06s
INFO | --- Analysis for jrc-names-ec took 4.916878700256348s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.0603859424591064s
Availability | VoID file availability check for JRC-Names-MLODE took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.28185153007507324s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.937980651855469e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 6.67572021484375e-06s
INFO | --- Analysis for jrc-names-mlode took 3.8256003856658936s
Availability | SPARQL endpoint availability check for JudaicaLink took 6.914138793945312e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.28481006622314453s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020810842514038086s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00011014938354492188s
Believability | Calculation of trust value for JudaicaLink took 6.67572021484375e-06s
INFO | --- Analysis for judaicalink took 7.140475034713745s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.0531158447265625e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.29782795906066895s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 2.7894973754882812e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 6.4373016357421875e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 3.111281633377075s
Availability | SPARQL endpoint availability check for KAKEN took 4.76837158203125e-05s
Availability | VoID file availability check for KAKEN took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for KAKEN took 0.2801628112792969s
Reputation | Calculation of the PageRank for KAKEN took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for KAKEN took 2.8848648071289062e-05s
Believability | Calculation of trust value for KAKEN took 6.4373016357421875e-06s
INFO | --- Analysis for kaken took 3.092083692550659s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07150864601135254s
Availability | VoID file availability check for Kallikratis municipalities took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.28411388397216797s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.02155780792236328s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.202957153320312e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.0067901611328125e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.626528739929199s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.2438507080078125e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.28461146354675293s
Reputation | Calculation of the PageRank for Openflights Routes took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 2.9802322387695312e-05s
Believability | Calculation of trust value for Openflights Routes took 7.3909759521484375e-06s
INFO | --- Analysis for kasabi-openflights-routes took 3.1714539527893066s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.2438507080078125e-05s
Availability | VoID file availability check for EU Soccer League took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.28433823585510254s
Reputation | Calculation of the PageRank for EU Soccer League took 0.021091461181640625s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0009670257568359375s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.8623809814453125e-05s
Believability | Calculation of trust value for EU Soccer League took 7.62939453125e-06s
INFO | --- Analysis for KG:Course_Submission took 3.7824792861938477s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.220008850097656e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.28386521339416504s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1205673217773438e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for KING took 2.768479824066162s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 5.745887756347656e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.28316497802734375s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.651878356933594e-05s
Believability | Calculation of trust value for Klappstuhlclub took 8.58306884765625e-06s
INFO | --- Analysis for klappstuhlclub took 12.775252103805542s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.881283283233643s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.28945374488830566s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.580352783203125e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 6.9141387939453125e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.92464303970337s
Availability | SPARQL endpoint availability check for Knowledge Forest took 3.9577484130859375e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2823514938354492s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.8371810913085938e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.67572021484375e-06s
INFO | --- Analysis for knowledge-map took 3.1674444675445557s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.458427429199219e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2686734199523926s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.9802322387695312e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.1444091796875e-05s
INFO | --- Analysis for KnowledgeFusion took 2.5054707527160645s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2888040542602539s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.556510925292969e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 7.62939453125e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.561268329620361s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.0531158447265625e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.2812924385070801s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.123283386230469e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 6.67572021484375e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 3.1211376190185547s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.7206878662109375e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.279613733291626s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.0040740966796875e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 7.3909759521484375e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.5503904819488525s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.029273986816406e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.26700782775878906s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 2.8848648071289062e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 6.9141387939453125e-06s
INFO | --- Analysis for ktr took 3.0905306339263916s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.363059997558594e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2837483882904053s
Reputation | Calculation of the PageRank for Informatics Studies took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.956390380859375e-05s
Believability | Calculation of trust value for Informatics Studies took 6.4373016357421875e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.2887938022613525s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.07657694816589355s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.552278995513916s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.28687453269958496s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02028822898864746s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 4.6253204345703125e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.2636184692382812e-05s
INFO | --- Analysis for kupkb took 6.7628014087677s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.220008850097656e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.2865104675292969s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.0994415283203125e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 6.9141387939453125e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 3.130441427230835s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 7.658036947250366s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.28315043449401855s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.486343383789062e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 6.4373016357421875e-06s
INFO | --- Analysis for l3s-dblp took 46.29985547065735s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 24.054785013198853s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.28447866439819336s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 8.845329284667969e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 7.152557373046875e-06s
INFO | --- Analysis for lak-dataset took 67.39955139160156s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.32567358016967773s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005114078521728516s
Extra | Recovery of all triples for  Language Name Authority List  took 93.1198399066925s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6148567199707031s
Amount of data | Number of triples check for  Language Name Authority List  took 93.48550462722778s
Interoperability | New terms check for  Language Name Authority List  took 110.1616325378418s
Versatility | Languages check for  Language Name Authority List  took 300.0876350402832s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 1.109710454940796s
Security | Check HTTPS for  Language Name Authority List  took 0.3299984931945801s
Interpretability | RDF structures check for  Language Name Authority List  took 0.3175466060638428s
Versatility | Serialization formats check for  Language Name Authority List  took 3.9379560947418213s
Availability | RDF dump link check for  Language Name Authority List  took 0.299562931060791s
License | MR license check for  Language Name Authority List  took 0.23853468894958496s
License | HR license check for  Language Name Authority List  took 300.08454513549805s
Amount of data | Number of property check for  Language Name Authority List  took 0.17735528945922852s
Understandability | Number of label check for  Language Name Authority List  took 6.056990623474121s
Understandability | URI regex check for  Language Name Authority List  took 0.2582387924194336s
Understandability | Vocabs check for  Language Name Authority List  took 0.1334536075592041s
Verifiability | Authors check for  Language Name Authority List  took 0.21047091484069824s
Verifiability | Publishers check for  Language Name Authority List  took 0.2649838924407959s
Performance | Throughput check for  Language Name Authority List  took 10.588849782943726s
Amount of data | Check the number of entities for  Language Name Authority List  took 0.00011348724365234375s
Verifiability | Contribs. check for  Language Name Authority List  took 0.21802258491516113s
Interlinking | sameAs chians check for  Language Name Authority List  took 9.505152463912964s
Interlinking | skos check for  Language Name Authority List  took 0.4286465644836426s
Interlinking | skos check for  Language Name Authority List  took 0.4582552909851074s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.19402837753295898s
Currency | Creation date check for  Language Name Authority List  took 0.3404390811920166s
Currency | Modification date check for  Language Name Authority List  took 0.23718500137329102s
Rep.Conc. | URIs length for  Language Name Authority List  took 487.7160601615906s
Interoperability | New vocabularies check for  Language Name Authority List  took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.2085871696472168s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.20900392532348633s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.16527819633483887s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 32.06235480308533s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.1239213943481445s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.816326856613159s
Consistency | Disjoint class check for  Language Name Authority List  took 0.1376490592956543s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.46355843544006s
Consistency | Misplaced classes for  Language Name Authority List  took 8.536075592041016s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 49.082157373428345s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 11.490310192108154s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.43614983558655s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.0550334453582764s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.5945205688476562s
Security | Sign check for  Language Name Authority List  took 0.1320791244506836s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 4.529513359069824s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.5813875198364258s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.020997047424316406s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.894371032714844e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 2.6226043701171875e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 8.106231689453125e-06s
INFO | --- Analysis for language-authority-list took 15480.712563991547s
Availability | SPARQL endpoint availability check for Lark took 384.33452439308167s
Availability | VoID file availability check for Lark took 0.000797271728515625s
Completeness | Calculation of interlinking completeness for Lark took 1.0203611850738525s
Reputation | Calculation of the PageRank for Lark took 0.021151065826416016s
Interlinking | Calculation of Degree of Connection for Lark took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Lark took 8.749961853027344e-05s
Believability | Calculation of trust value for Lark took 8.58306884765625e-06s
INFO | --- Analysis for LARK took 1679.5247344970703s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.524918794631958s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.7130167484283447s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for LASLA took 7.341519594192505s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.38690185546875e-05s
Availability | VoID file availability check for LATC Linksets took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.7161269187927246s
Reputation | Calculation of the PageRank for LATC Linksets took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.266334533691406e-05s
Believability | Calculation of trust value for LATC Linksets took 6.9141387939453125e-06s
INFO | --- Analysis for latc-linksets took 5.370677709579468s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.41757631301879883s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.3005695343017578s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.124641418457031e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 6.067293405532837s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.4093897342681885s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.30252838134765625s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LatinAffectus took 4.285897254943848s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.408449649810791s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.287095308303833s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.0531158447265625e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 8.58306884765625e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.786840200424194s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.291534423828125e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.28377532958984375s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020834684371948242s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 2.956390380859375e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 8.106231689453125e-06s
INFO | --- Analysis for lcc took 4.179678678512573s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.673004150390625e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2854628562927246s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011658668518066406s
Believability | Calculation of trust value for Library of Congress Subject Headings took 6.9141387939453125e-06s
INFO | --- Analysis for lcsh took 6.12618613243103s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 5.1021575927734375e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2865931987762451s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.416175842285156e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.62939453125e-06s
INFO | --- Analysis for lcsubjects took 2.7835655212402344s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 6.270408630371094e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.26987266540527344s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 2.9802322387695312e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 7.152557373046875e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 3.1504907608032227s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.782087802886963s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.2936985492706299s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.57763671875e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.2159347534179688e-05s
INFO | --- Analysis for ldt@library took 37.06328749656677s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.100799560546875e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.28341031074523926s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 2.8133392333984375e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 1.2874603271484375e-05s
INFO | --- Analysis for learned-genre-ontology-eng took 3.117919445037842s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.100799560546875e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.28099894523620605s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.02030467987060547s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.6941299438476562e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 6.4373016357421875e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 3.1356101036071777s
Availability | SPARQL endpoint availability check for U ime Legije took 4.267692565917969e-05s
Availability | VoID file availability check for U ime Legije took 0.000308990478515625s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.2824230194091797s
Reputation | Calculation of the PageRank for U ime Legije took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.62396240234375e-05s
Believability | Calculation of trust value for U ime Legije took 5.9604644775390625e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.536081552505493s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.076957702636719e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.2895214557647705s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 5.9604644775390625e-06s
INFO | --- Analysis for legislation-openuplabs took 3.1662821769714355s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.3823862075805664s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.2845168113708496s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02023029327392578s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.081031799316406e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 7.152557373046875e-06s
INFO | --- Analysis for LemmaBank took 4.629067420959473s
Availability | SPARQL endpoint availability check for lemonUby took 4.172325134277344e-05s
Availability | VoID file availability check for lemonUby took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2875099182128906s
Reputation | Calculation of the PageRank for lemonUby took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.270408630371094e-05s
Believability | Calculation of trust value for lemonUby took 7.62939453125e-06s
INFO | --- Analysis for lemonuby took 3.4683837890625s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.267692565917969e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.2835524082183838s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.528594970703125e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.62939453125e-06s
INFO | --- Analysis for lemonwiktionary took 4.415941476821899s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.4325573444366455s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.3034648895263672s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for LewisShort took 4.189795255661011s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.0126800537109375s
Availability | VoID file availability check for LEXIN-RDF took 0.00041031837463378906s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2827913761138916s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for LEXIN-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for lexin-rdf took 5.802204370498657s
Availability | SPARQL endpoint availability check for lexinfo took 5.412101745605469e-05s
Availability | VoID file availability check for lexinfo took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2853109836578369s
Reputation | Calculation of the PageRank for lexinfo took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for lexinfo took 9.059906005859375e-05s
Believability | Calculation of trust value for lexinfo took 1.1444091796875e-05s
INFO | --- Analysis for lexinfo took 2.98860502243042s
Availability | SPARQL endpoint availability check for Lexvo took 4.315376281738281e-05s
Availability | VoID file availability check for Lexvo took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Lexvo took 0.302384614944458s
Reputation | Calculation of the PageRank for Lexvo took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00018525123596191406s
Believability | Calculation of trust value for Lexvo took 7.62939453125e-06s
INFO | --- Analysis for lexvo took 3.1913061141967773s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.172325134277344e-05s
Availability | VoID file availability check for Lexvo.org took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.25942039489746094s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020711421966552734s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0008637905120849609s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.557868957519531e-05s
Believability | Calculation of trust value for Lexvo.org took 7.3909759521484375e-06s
INFO | --- Analysis for lexvo-org took 2.6374008655548096s
Availability | SPARQL endpoint availability check for LIBRIS took 0.39911508560180664s
Availability | VoID file availability check for LIBRIS took 0.00034117698669433594s
Extra | Recovery of all triples for LIBRIS took 19.40956449508667s
Performance | Total latancy measurement for LIBRIS took 0.7384796142578125s
Amount of data | Number of triples check for LIBRIS took 22.805819988250732s
Interoperability | New terms check for LIBRIS took 15.894945621490479s
Versatility | Languages check for LIBRIS took 0.19072484970092773s
Interpretability | Number of blank nodes check for LIBRIS took 300.0985028743744s
Security | Check HTTPS for LIBRIS took 0.3696320056915283s
Interpretability | RDF structures check for LIBRIS took 0.2666037082672119s
Versatility | Serialization formats check for LIBRIS took 0.23760104179382324s
Availability | RDF dump link check for LIBRIS took 0.14796185493469238s
License | MR license check for LIBRIS took 0.22771573066711426s
License | HR license check for LIBRIS took 1.2104015350341797s
Amount of data | Number of property check for LIBRIS took 0.20032286643981934s
Understandability | Number of label check for LIBRIS took 0.39971280097961426s
Understandability | URI regex check for LIBRIS took 0.3075563907623291s
Understandability | Vocabs check for LIBRIS took 0.14914298057556152s
Verifiability | Authors check for LIBRIS took 0.15675997734069824s
Verifiability | Publishers check for LIBRIS took 0.15426182746887207s
Amount of data | Check the number of entities for LIBRIS took 0.00011038780212402344s
Verifiability | Contribs. check for LIBRIS took 0.16087007522583008s
Interlinking | sameAs chians check for LIBRIS took 0.13701939582824707s
Interlinking | skos check for LIBRIS took 0.1947777271270752s
Interlinking | skos check for LIBRIS took 0.1459977626800537s
Timeliness | dataset update frequency check for LIBRIS took 0.16189789772033691s
Currency | Creation date check for LIBRIS took 0.3676033020019531s
Currency | Modification date check for LIBRIS took 0.6442837715148926s
Rep.Conc. | URIs length for LIBRIS took 84.67894625663757s
Interoperability | New vocabularies check for LIBRIS took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.190260648727417s
Accuracy | Check Functional Property for LIBRIS took 0.21262240409851074s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.15949583053588867s
Accuracy | Check Datatype consistency for LIBRIS took 0.2792060375213623s
Consistency | Disjoint class check for LIBRIS took 0.19161438941955566s
Consistency | Check Misplaced properties for LIBRIS took 62.019775390625s
Consistency | Misplaced classes for LIBRIS took 1.1654813289642334s
Consistency | Check Ontology hijacking for LIBRIS took 6.454253673553467s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1647875308990479s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 62.6974880695343s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2899458408355713s
Conciseness | Check Intensional conciseness for LIBRIS took 0.42283201217651367s
Security | Sign check for LIBRIS took 0.2295851707458496s
Availability | Check URIs Dereferenciability for LIBRIS took 9.48678207397461s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.275045394897461s
Reputation | Calculation of the PageRank for LIBRIS took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.202957153320312e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.6689300537109375e-06s
Believability | Calculation of trust value for LIBRIS took 1.0967254638671875e-05s
INFO | --- Analysis for libris took 1101.2121596336365s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.07261800765991211s
Availability | VoID file availability check for Public Library of Veroia took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.7334342002868652s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 8.296966552734375e-05s
Believability | Calculation of trust value for Public Library of Veroia took 7.152557373046875e-06s
INFO | --- Analysis for libver took 6.750542163848877s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.10757255554199219s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.7163975238800049s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.392333984375e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 7.867813110351562e-06s
INFO | --- Analysis for lichfield-spending took 4.460596084594727s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.3392181396484375e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.7342402935028076s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020344972610473633s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.504753112792969e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 6.9141387939453125e-06s
INFO | --- Analysis for lime took 7.525398254394531s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.458427429199219e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.3084685802459717s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010967254638671875s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.3909759521484375e-06s
INFO | --- Analysis for lingvoj took 8.667951583862305s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2863945960998535s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.058547973632812e-05s
Believability | Calculation of trust value for Linked Crunchbase took 7.152557373046875e-06s
INFO | --- Analysis for linked-crunchbase took 2.9832301139831543s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.296187400817871s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.00039458274841308594s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.298642635345459s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.748603820800781e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.152557373046875e-06s
INFO | --- Analysis for linked-drugs took 20.86352777481079s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.291534423828125e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.282883882522583s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.00010275840759277344s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 4.76837158203125e-06s
INFO | --- Analysis for linked-edgar took 4.342881441116333s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 5.53131103515625e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.28275609016418457s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02028822898864746s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.703636169433594e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-eurostat took 3.5889148712158203s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.38690185546875e-05s
Availability | VoID file availability check for linked hypernyms took 0.0013217926025390625s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2881748676300049s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.915496826171875e-05s
Believability | Calculation of trust value for linked hypernyms took 9.775161743164062e-06s
INFO | --- Analysis for linked-hypernyms took 4.0113205909729s
Availability | SPARQL endpoint availability check for Linked Life Data took 209.21248841285706s
Availability | VoID file availability check for Linked Life Data took 0.0008089542388916016s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.949324369430542s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020778656005859375s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.054473876953125e-05s
Believability | Calculation of trust value for Linked Life Data took 7.867813110351562e-06s
INFO | --- Analysis for linked-life-data took 670.5766112804413s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.3938119411468506s
Availability | VoID file availability check for Linked Logainm took 0.0005462169647216797s
Extra | Recovery of all triples for Linked Logainm took 2.6085572242736816s
Performance | Total latancy measurement for Linked Logainm took 0.6256816387176514s
Amount of data | Number of triples check for Linked Logainm took 0.19344568252563477s
Interoperability | New terms check for Linked Logainm took 1.3593835830688477s
Versatility | Languages check for Linked Logainm took 1.8004751205444336s
Interpretability | Number of blank nodes check for Linked Logainm took 0.16595816612243652s
Security | Check HTTPS for Linked Logainm took 0.29508471488952637s
Interpretability | RDF structures check for Linked Logainm took 0.4498484134674072s
Versatility | Serialization formats check for Linked Logainm took 0.17976737022399902s
Availability | RDF dump link check for Linked Logainm took 0.12411379814147949s
License | MR license check for Linked Logainm took 0.13704133033752441s
License | HR license check for Linked Logainm took 0.2234177589416504s
Amount of data | Number of property check for Linked Logainm took 0.15861964225769043s
Understandability | Number of label check for Linked Logainm took 0.2062530517578125s
Understandability | URI regex check for Linked Logainm took 0.2512247562408447s
Understandability | Vocabs check for Linked Logainm took 0.12173867225646973s
Verifiability | Authors check for Linked Logainm took 0.12751173973083496s
Verifiability | Publishers check for Linked Logainm took 0.12111067771911621s
Performance | Throughput check for Linked Logainm took 10.725626230239868s
Amount of data | Check the number of entities for Linked Logainm took 7.963180541992188e-05s
Verifiability | Contribs. check for Linked Logainm took 0.12496447563171387s
Interlinking | sameAs chians check for Linked Logainm took 0.15945124626159668s
Interlinking | skos check for Linked Logainm took 0.16699910163879395s
Interlinking | skos check for Linked Logainm took 0.11969923973083496s
Timeliness | dataset update frequency check for Linked Logainm took 0.1297919750213623s
Currency | Creation date check for Linked Logainm took 0.291776180267334s
Currency | Modification date check for Linked Logainm took 0.2918531894683838s
Rep.Conc. | URIs length for Linked Logainm took 1.390303373336792s
Interoperability | New vocabularies check for Linked Logainm took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.15077471733093262s
Accuracy | Check Functional Property for Linked Logainm took 0.23154711723327637s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.20241880416870117s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.683387279510498s
Accuracy | Check White space in annotation for Linked Logainm took 0.030814647674560547s
Accuracy | Check Datatype consistency for Linked Logainm took 0.029787540435791016s
Consistency | Disjoint class check for Linked Logainm took 0.19980120658874512s
Consistency | Check Misplaced properties for Linked Logainm took 0.38066649436950684s
Consistency | Misplaced classes for Linked Logainm took 0.29433703422546387s
Consistency | Check Ontology hijacking for Linked Logainm took 1.8262736797332764s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.18381667137146s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.4066352844238281s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03131389617919922s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.21738266944885254s
Security | Sign check for Linked Logainm took 0.13629627227783203s
Availability | Check URIs Dereferenciability for Linked Logainm took 1072.6492125988007s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.9076950550079346s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.0108642578125e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Logainm took 7.867813110351562e-06s
INFO | --- Analysis for linked-logainm took 1134.3559246063232s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.291534423828125e-05s
Availability | VoID file availability check for Linked NUTS took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.7336511611938477s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02120685577392578s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.3882598876953125e-05s
Believability | Calculation of trust value for Linked NUTS took 5.7220458984375e-06s
INFO | --- Analysis for linked-nuts took 4.914003372192383s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 5.53131103515625e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.7402682304382324s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020308494567871094s
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.0007224082946777344s
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.62939453125e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 4.970887660980225s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.8239591121673584s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.28807806968688965s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020229339599609375s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.24249267578125e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-camera took 4.605481386184692s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.560764789581299s
Availability | VoID file availability check for Linked Open Commerce took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2850637435913086s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0009305477142333984s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.719329833984375e-05s
Believability | Calculation of trust value for Linked Open Commerce took 8.821487426757812e-06s
INFO | --- Analysis for linked-open-commerce took 15.186121225357056s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.7182388305664062s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.29811549186706543s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010228157043457031s
Believability | Calculation of trust value for Linked Open Data of Ecology took 6.198883056640625e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 4.407673120498657s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.410743713378906e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2846548557281494s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.012222290039062e-05s
Believability | Calculation of trust value for Linked Open Numbers took 6.4373016357421875e-06s
INFO | --- Analysis for linked-open-numbers took 2.8079659938812256s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.29512524604797363s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.9604644775390625e-06s
INFO | --- Analysis for linked-open-piracy took 6.676802635192871s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 5.316734313964844e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2620089054107666s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.021015405654907227s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.000989675521850586s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-senate took 3.082139253616333s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.2083263397216797s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.28284311294555664s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 5.7697296142578125e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 7.62939453125e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 7.024642467498779s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.30773115158081055s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.245208740234375e-06s
INFO | --- Analysis for linked-periodicals took 2.7950053215026855s
Availability | SPARQL endpoint availability check for Linked Index took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Index took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Linked Index took 0.27455973625183105s
Reputation | Calculation of the PageRank for Linked Index took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.082389831542969e-05s
Believability | Calculation of trust value for Linked Index took 5.9604644775390625e-06s
INFO | --- Analysis for linked-stockindex took 2.631514310836792s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.303220987319946s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.30443406105041504s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.62396240234375e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 7.867813110351562e-06s
INFO | --- Analysis for linked-structured-product-labels took 13.574578523635864s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.9414162635803223s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.272214412689209s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020681142807006836s
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.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.3855438232421875e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 6.4373016357421875e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 3.6514344215393066s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.294918537139893s
Availability | VoID file availability check for Linked TCGA took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.299114465713501s
Reputation | Calculation of the PageRank for Linked TCGA took 0.021054506301879883s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0008449554443359375s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 0.0001010894775390625s
Believability | Calculation of trust value for Linked TCGA took 8.58306884765625e-06s
INFO | --- Analysis for linked-tcga took 62.86508369445801s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.09283661842346191s
Availability | VoID file availability check for Linked User Feedback took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.2852516174316406s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020284175872802734s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 4.4345855712890625e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.2159347534179688e-05s
INFO | --- Analysis for linked-user-feedback took 2.7456836700439453s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.5299530029296875e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.27507448196411133s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020209550857543945s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.462501525878906e-05s
Believability | Calculation of trust value for USPTO Patent data took 7.867813110351562e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.38312768936157s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2808544635772705s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007383823394775391s
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 3.1341559886932373s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.220008850097656e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.29494714736938477s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 2.8371810913085938e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 6.9141387939453125e-06s
INFO | --- Analysis for linkedarc took 3.122349500656128s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.09874725341796875s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.28717613220214844s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.838539123535156e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 7.152557373046875e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.9961137771606445s
Availability | SPARQL endpoint availability check for LinkedCT took 1.5026280879974365s
Availability | VoID file availability check for LinkedCT took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.2859067916870117s
Reputation | Calculation of the PageRank for LinkedCT took 0.020390987396240234s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00014066696166992188s
Believability | Calculation of trust value for LinkedCT took 7.3909759521484375e-06s
INFO | --- Analysis for linkedct took 5.8325910568237305s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.23471808433532715s
Availability | VoID file availability check for LinkedGeoData took 0.00041985511779785156s
Extra | Recovery of all triples for LinkedGeoData took 15.611074209213257s
Performance | Total latancy measurement for LinkedGeoData took 0.7379484176635742s
Amount of data | Number of triples check for LinkedGeoData took 46.83333110809326s
Interoperability | New terms check for LinkedGeoData took 91.82793879508972s
Versatility | Languages check for LinkedGeoData took 181.2331840991974s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.24676823616027832s
Security | Check HTTPS for LinkedGeoData took 0.34920287132263184s
Interpretability | RDF structures check for LinkedGeoData took 0.7930459976196289s
Versatility | Serialization formats check for LinkedGeoData took 0.3516974449157715s
Availability | RDF dump link check for LinkedGeoData took 0.16562223434448242s
License | MR license check for LinkedGeoData took 0.5902533531188965s
License | HR license check for LinkedGeoData took 87.79035186767578s
Amount of data | Number of property check for LinkedGeoData took 0.23017311096191406s
Understandability | Number of label check for LinkedGeoData took 2.0072007179260254s
Understandability | URI regex check for LinkedGeoData took 0.4045717716217041s
Understandability | Vocabs check for LinkedGeoData took 0.19084763526916504s
Verifiability | Authors check for LinkedGeoData took 0.17558979988098145s
Verifiability | Publishers check for LinkedGeoData took 0.15241193771362305s
Performance | Throughput check for LinkedGeoData took 10.860520839691162s
Amount of data | Check the number of entities for LinkedGeoData took 0.06517624855041504s
Verifiability | Contribs. check for LinkedGeoData took 1.8971030712127686s
Interlinking | sameAs chians check for LinkedGeoData took 0.3224799633026123s
Interlinking | skos check for LinkedGeoData took 0.41711997985839844s
Interlinking | skos check for LinkedGeoData took 0.14014840126037598s
Timeliness | dataset update frequency check for LinkedGeoData took 0.37940073013305664s
Currency | Creation date check for LinkedGeoData took 0.5031778812408447s
Currency | Modification date check for LinkedGeoData took 2.2930753231048584s
Rep.Conc. | URIs length for LinkedGeoData took 272.2218918800354s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.17870712280273438s
Accuracy | Check Functional Property for LinkedGeoData took 0.22516179084777832s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.19192194938659668s
Accuracy | Check Empty annotation labels for LinkedGeoData took 3.062011480331421s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15918350219726562s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13804984092712402s
Consistency | Disjoint class check for LinkedGeoData took 0.23045969009399414s
Consistency | Check Misplaced properties for LinkedGeoData took 181.80707216262817s
Consistency | Misplaced classes for LinkedGeoData took 0.676522970199585s
Consistency | Check Ontology hijacking for LinkedGeoData took 4.850515842437744s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.1682031154632568s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.9972665309906s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.14678955078125s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.4024779796600342s
Security | Sign check for LinkedGeoData took 0.6447820663452148s
Availability | Check URIs Dereferenciability for LinkedGeoData took 10.506883144378662s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.9868199825286865s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021053552627563477s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00013375282287597656s
Believability | Calculation of trust value for LinkedGeoData took 8.344650268554688e-06s
INFO | --- Analysis for linkedgeodata took 2161.7615020275116s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.744529724121094e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.7512478828430176s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020882368087768555s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.24249267578125e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 7.62939453125e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 6.064027547836304s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.105363368988037s
Availability | VoID file availability check for LinkedLCCN took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.2731490135192871s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00011205673217773438s
Believability | Calculation of trust value for LinkedLCCN took 8.344650268554688e-06s
INFO | --- Analysis for linkedlccn took 20.459493160247803s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.291534423828125e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.7238092422485352s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.5762786865234375e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.0728836059570312e-05s
INFO | --- Analysis for linkedmarkmail took 3.1481218338012695s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.64342141151428s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.3014557361602783s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013065338134765625s
Believability | Calculation of trust value for Linked Movie DataBase took 7.3909759521484375e-06s
INFO | --- Analysis for linkedmdb took 134.0584864616394s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.4984283447265625s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.28887152671813965s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.867813110351562e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 8.821487426757812e-06s
INFO | --- Analysis for linkedspending took 5.294577360153198s
Availability | SPARQL endpoint availability check for LinkedStats took 4.076957702636719e-05s
Availability | VoID file availability check for LinkedStats took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.27055811882019043s
Reputation | Calculation of the PageRank for LinkedStats took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 2.9802322387695312e-05s
Believability | Calculation of trust value for LinkedStats took 7.152557373046875e-06s
INFO | --- Analysis for linkedstats took 4.032010555267334s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.076957702636719e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.000244140625s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.2895009517669678s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.4332275390625e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 7.152557373046875e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 3.1532437801361084s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 8.177757263183594e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.2778041362762451s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 2.956390380859375e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 1.1444091796875e-05s
INFO | --- Analysis for linking-open-drug-data took 3.5334036350250244s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.05829143524169922s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.2850935459136963s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010752677917480469s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 7.867813110351562e-06s
INFO | --- Analysis for linklion took 2.686647415161133s
Availability | SPARQL endpoint availability check for Lion's Den took 6.985664367675781e-05s
Availability | VoID file availability check for Lion's Den took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.27723073959350586s
Reputation | Calculation of the PageRank for Lion's Den took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0010156631469726562s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 4.1484832763671875e-05s
Believability | Calculation of trust value for Lion's Den took 7.3909759521484375e-06s
INFO | --- Analysis for lionsden took 3.092757225036621s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 33.952656269073486s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2876555919647217s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020566463470458984s
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.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 4.982948303222656e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 6.198883056640625e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 40.00817608833313s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.673004150390625e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.28440093994140625s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020775318145751953s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 6.9141387939453125e-06s
INFO | --- Analysis for livtdm took 3.6282989978790283s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.124641418457031e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.27945518493652344s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.075599670410156e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 8.106231689453125e-06s
INFO | --- Analysis for livtdm2017 took 3.985351324081421s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.2840549945831299s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.075599670410156e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.152557373046875e-06s
INFO | --- Analysis for lobi took 3.5890822410583496s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.2045681476593018s
Availability | VoID file availability check for lobid-organisations took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.27185869216918945s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.655952453613281e-05s
Believability | Calculation of trust value for lobid-organisations took 6.4373016357421875e-06s
INFO | --- Analysis for lobid-organisations took 6.383390188217163s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.9840502738952637s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.3014869689941406s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020270347595214844s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.846687316894531e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 9.775161743164062e-06s
INFO | --- Analysis for lobid-resources took 8.60968279838562s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.29509401321411133s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 8.130073547363281e-05s
Believability | Calculation of trust value for Linked Open Colors took 7.152557373046875e-06s
INFO | --- Analysis for loc took 7.586787700653076s
Availability | SPARQL endpoint availability check for Location Ontology took 6.175041198730469e-05s
Availability | VoID file availability check for Location Ontology took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.3046534061431885s
Reputation | Calculation of the PageRank for Location Ontology took 0.020334243774414062s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Location Ontology took 6.67572021484375e-06s
INFO | --- Analysis for Location_Ontology took 3.734539031982422s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.458427429199219e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.3437321186065674s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.02028965950012207s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 7.62939453125e-06s
INFO | --- Analysis for locv took 33.89083981513977s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.8238050937652588s
Availability | VoID file availability check for LOD-a-lot took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2846386432647705s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.147125244140625e-05s
Believability | Calculation of trust value for LOD-a-lot took 8.58306884765625e-06s
INFO | --- Analysis for lod-a-lot took 14.2598135471344s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.172325134277344e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.3008694648742676s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02038407325744629s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 1.0967254638671875e-05s
INFO | --- Analysis for lod-it_scuole-italiane took 3.1427714824676514s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.0531158447265625e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.2843306064605713s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.239776611328125e-05s
INFO | --- Analysis for lod-taiwan took 3.125016212463379s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.3392181396484375e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.28822755813598633s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02025771141052246s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 0.00010895729064941406s
Believability | Calculation of trust value for LOD2 Project Wiki took 7.152557373046875e-06s
INFO | --- Analysis for lod2-project-wiki took 3.893390417098999s
Availability | SPARQL endpoint availability check for LODAC BDLS took 3.092125415802002s
Availability | VoID file availability check for LODAC BDLS took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.28638267517089844s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.343292236328125e-05s
Believability | Calculation of trust value for LODAC BDLS took 6.4373016357421875e-06s
INFO | --- Analysis for lodac-bdls took 14.386776685714722s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.172325134277344e-05s
Availability | VoID file availability check for LODRussia Math took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2886805534362793s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.9087066650390625e-05s
Believability | Calculation of trust value for LODRussia Math took 7.152557373046875e-06s
INFO | --- Analysis for lodrussia-math took 3.114166498184204s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.220008850097656e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.266512393951416s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 2.956390380859375e-05s
Believability | Calculation of trust value for LODRussia Nano took 6.198883056640625e-06s
INFO | --- Analysis for lodrussia-nano took 3.1131813526153564s
Availability | SPARQL endpoint availability check for LODStats took 5.2928924560546875e-05s
Availability | VoID file availability check for LODStats took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for LODStats took 0.2846343517303467s
Reputation | Calculation of the PageRank for LODStats took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for LODStats took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.075599670410156e-05s
Believability | Calculation of trust value for LODStats took 7.867813110351562e-06s
INFO | --- Analysis for lodstats took 3.173025369644165s
Availability | SPARQL endpoint availability check for LODUM took 4.1961669921875e-05s
Availability | VoID file availability check for LODUM took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for LODUM took 0.2826099395751953s
Reputation | Calculation of the PageRank for LODUM took 0.020333528518676758s
Interlinking | Calculation of Degree of Connection for LODUM took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.8133392333984375e-05s
Believability | Calculation of trust value for LODUM took 6.67572021484375e-06s
INFO | --- Analysis for lodum took 3.128920078277588s
Availability | SPARQL endpoint availability check for lofd took 0.13258981704711914s
Availability | VoID file availability check for lofd took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for lofd took 0.2948172092437744s
Reputation | Calculation of the PageRank for lofd took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for lofd took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for lofd took 2.8371810913085938e-05s
Believability | Calculation of trust value for lofd took 6.9141387939453125e-06s
INFO | --- Analysis for lofd took 2.7236757278442383s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 272.2160370349884s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2859814167022705s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.020397424697875977s
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.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.14984130859375e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 5.4836273193359375e-06s
INFO | --- Analysis for loius took 586.7318160533905s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 5.745887756347656e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.28196001052856445s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02100205421447754s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.7894973754882812e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 7.62939453125e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 5.405401945114136s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 1.8268554210662842s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2861051559448242s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02031683921813965s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.269050598144531e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.4836273193359375e-06s
INFO | --- Analysis for london-gazette took 9.075464248657227s
Availability | SPARQL endpoint availability check for Weather Stations took 0.00047850608825683594s
Availability | VoID file availability check for Weather Stations took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.7567718029022217s
Reputation | Calculation of the PageRank for Weather Stations took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.058547973632812e-05s
Believability | Calculation of trust value for Weather Stations took 6.9141387939453125e-06s
INFO | --- Analysis for los_metar took 4.856952667236328s
Availability | SPARQL endpoint availability check for Lotico took 1.0168006420135498s
Availability | VoID file availability check for Lotico took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Lotico took 0.753758430480957s
Reputation | Calculation of the PageRank for Lotico took 0.02019500732421875s
Interlinking | Calculation of Degree of Connection for Lotico took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0008625984191894531s
Interlinking | Calculation of Clustering coefficient for Lotico took 9.012222290039062e-05s
Believability | Calculation of trust value for Lotico took 5.9604644775390625e-06s
INFO | --- Analysis for lotico took 8.144363641738892s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.4277663230895996s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.7133169174194336s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02152228355407715s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.001203298568725586s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 4.291534423828125e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.2159347534179688e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 5.606635808944702s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 391.95407128334045s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00039076805114746094s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.30260634422302246s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.506111145019531e-05s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for LPIS_(Poland) took 666.9563944339752s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 393.6582100391388s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.28826403617858887s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.020595550537109375s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.838539123535156e-05s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 671.6021535396576s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 7.653236389160156e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 1.079383373260498s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.023412227630615234s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.075599670410156e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 7.152557373046875e-06s
INFO | --- Analysis for lremap-auth took 29.89924693107605s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 7.367134094238281e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2851228713989258s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.695487976074219e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 8.344650268554688e-06s
INFO | --- Analysis for lremap-conf took 16.83958649635315s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 5.5789947509765625e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.28229856491088867s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.075599670410156e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 8.106231689453125e-06s
INFO | --- Analysis for lremap-ri took 15.913043737411499s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.2438507080078125e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.7882680892944336s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.075599670410156e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 7.867813110351562e-06s
INFO | --- Analysis for lremap-sub took 15.522895336151123s
Availability | SPARQL endpoint availability check for LSQ took 4.3392181396484375e-05s
Availability | VoID file availability check for LSQ took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for LSQ took 0.2855212688446045s
Reputation | Calculation of the PageRank for LSQ took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for LSQ took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.1948089599609375e-05s
Believability | Calculation of trust value for LSQ took 7.62939453125e-06s
INFO | --- Analysis for lsq took 4.667539119720459s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.543816089630127s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.28942298889160156s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 8.58306884765625e-06s
INFO | --- Analysis for LucaniPharsalia took 4.7305006980896s
Availability | SPARQL endpoint availability check for Linked rules took 6.890296936035156e-05s
Availability | VoID file availability check for Linked rules took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Linked rules took 0.28389501571655273s
Reputation | Calculation of the PageRank for Linked rules took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0008347034454345703s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.266334533691406e-05s
Believability | Calculation of trust value for Linked rules took 1.1920928955078125e-05s
INFO | --- Analysis for Luminaires_senlis took 2.5544791221618652s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.482269287109375e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.28725409507751465s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.0994415283203125e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 8.106231689453125e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 3.5604405403137207s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.240320682525635s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.28290367126464844s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.886222839355469e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for makg took 63.63220405578613s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 5.5789947509765625e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.31364989280700684s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020084142684936523s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.266334533691406e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 6.67572021484375e-06s
INFO | --- Analysis for manchester-university-reading-lists took 4.712000370025635s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2807939052581787s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.62939453125e-06s
INFO | --- Analysis for manish took 2.5567166805267334s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.124641418457031e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.7952930927276611s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.86102294921875e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 7.3909759521484375e-06s
INFO | --- Analysis for mapa-referencia-bogota took 4.11242413520813s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.267692565917969e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.29953551292419434s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.170967102050781e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 8.106231689453125e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 3.1477625370025635s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.363059997558594e-05s
Availability | VoID file availability check for MARC Codes List took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2874159812927246s
Reputation | Calculation of the PageRank for MARC Codes List took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.0001251697540283203s
Believability | Calculation of trust value for MARC Codes List took 1.3113021850585938e-05s
INFO | --- Analysis for marc-codes took 13.857210874557495s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.315376281738281e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.29037976264953613s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.100799560546875e-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.258247375488281s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.3392181396484375e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.28640270233154297s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.933906555175781e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.2636184692382812e-05s
INFO | --- Analysis for masc-bn-nif took 2.6422247886657715s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.3106627464294434s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.28673386573791504s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.170967102050781e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 7.62939453125e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.782100439071655s
Availability | SPARQL endpoint availability check for medline took 4.482269287109375e-05s
Availability | VoID file availability check for medline took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for medline took 0.28648877143859863s
Reputation | Calculation of the PageRank for medline took 0.02125382423400879s
Interlinking | Calculation of Degree of Connection for medline took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for medline took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for medline took 3.647804260253906e-05s
Believability | Calculation of trust value for medline took 7.3909759521484375e-06s
INFO | --- Analysis for medline took 7.583028554916382s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.651045799255371s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2806985378265381s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 0.00010967254638671875s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 8.106231689453125e-06s
INFO | --- Analysis for meducator took 13.198130130767822s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.1484832763671875e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.29128599166870117s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 3.314018249511719e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.86102294921875e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 6.9141387939453125e-06s
INFO | --- Analysis for mesh-finnish took 3.207505226135254s
Availability | SPARQL endpoint availability check for MeSH headings took 4.172325134277344e-05s
Availability | VoID file availability check for MeSH headings took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.2835958003997803s
Reputation | Calculation of the PageRank for MeSH headings took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for MeSH headings took 4.1961669921875e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 3.147125244140625e-05s
Believability | Calculation of trust value for MeSH headings took 9.298324584960938e-06s
INFO | --- Analysis for mesh_headings took 3.1761281490325928s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.0003521442413330078s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2778658866882324s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0010957717895507812s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 4.100799560546875e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 6.9141387939453125e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 3.1258208751678467s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.076957702636719e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.30012035369873047s
Reputation | Calculation of the PageRank for MeSH pairs took 0.02143120765686035s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0011286735534667969s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 4.267692565917969e-05s
Believability | Calculation of trust value for MeSH pairs took 7.867813110351562e-06s
INFO | --- Analysis for mesh_pairs took 3.182786703109741s
Availability | SPARQL endpoint availability check for MeSH titles took 4.1961669921875e-05s
Availability | VoID file availability check for MeSH titles took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.2815251350402832s
Reputation | Calculation of the PageRank for MeSH titles took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.0279159545898438e-05s
Believability | Calculation of trust value for MeSH titles took 7.3909759521484375e-06s
INFO | --- Analysis for mesh_titles took 3.153040647506714s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.267692565917969e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2874562740325928s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.24249267578125e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 7.867813110351562e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 3.1867988109588623s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 5.555152893066406e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.28614187240600586s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0009953975677490234s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.00543212890625e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.344650268554688e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 3.1497488021850586s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.363059997558594e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.27150416374206543s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020296335220336914s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.866455078125e-05s
Believability | Calculation of trust value for MetaShare metadata model took 6.67572021484375e-06s
INFO | --- Analysis for metashare took 2.7818307876586914s
Availability | SPARQL endpoint availability check for MExiCo took 4.839897155761719e-05s
Availability | VoID file availability check for MExiCo took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2871367931365967s
Reputation | Calculation of the PageRank for MExiCo took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.553794860839844e-05s
Believability | Calculation of trust value for MExiCo took 6.4373016357421875e-06s
INFO | --- Analysis for mexico took 22.692020177841187s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0538718700408936s
Availability | VoID file availability check for Coronavirus dataset took 0.00024080276489257812s
Extra | Recovery of all triples for Coronavirus dataset took 11.492861986160278s
Performance | Total latancy measurement for Coronavirus dataset took 2.516828775405884s
Amount of data | Number of triples check for Coronavirus dataset took 1.1992087364196777s
Interoperability | New terms check for Coronavirus dataset took 2.487224578857422s
Versatility | Languages check for Coronavirus dataset took 60.52374863624573s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.4468915462493896s
Interpretability | RDF structures check for Coronavirus dataset took 0.5500597953796387s
Versatility | Serialization formats check for Coronavirus dataset took 0.5588035583496094s
Availability | RDF dump link check for Coronavirus dataset took 0.5002179145812988s
License | MR license check for Coronavirus dataset took 0.5728261470794678s
License | HR license check for Coronavirus dataset took 41.13904428482056s
Amount of data | Number of property check for Coronavirus dataset took 0.5384485721588135s
Understandability | Number of label check for Coronavirus dataset took 1.4349689483642578s
Understandability | URI regex check for Coronavirus dataset took 1.0064733028411865s
Understandability | Vocabs check for Coronavirus dataset took 0.5043251514434814s
Verifiability | Authors check for Coronavirus dataset took 0.5470983982086182s
Verifiability | Publishers check for Coronavirus dataset took 0.5097057819366455s
Performance | Throughput check for Coronavirus dataset took 14.46204662322998s
Amount of data | Check the number of entities for Coronavirus dataset took 7.2479248046875e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5047926902770996s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5463175773620605s
Interlinking | skos check for Coronavirus dataset took 0.5578491687774658s
Interlinking | skos check for Coronavirus dataset took 0.49958109855651855s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5148580074310303s
Currency | Creation date check for Coronavirus dataset took 1.0329890251159668s
Currency | Modification date check for Coronavirus dataset took 1.0338749885559082s
Rep.Conc. | URIs length for Coronavirus dataset took 9.508342266082764s
Interoperability | New vocabularies check for Coronavirus dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5289580821990967s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7962863445281982s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.6983067989349365s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.460750102996826s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022571563720703125s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.028201580047607422s
Consistency | Disjoint class check for Coronavirus dataset took 1.158752202987671s
Consistency | Check Misplaced properties for Coronavirus dataset took 8.669144630432129s
Consistency | Misplaced classes for Coronavirus dataset took 0.6237728595733643s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.9418885707855225s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.145456314086914s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.674249172210693s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.031487226486206055s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5377151966094971s
Security | Sign check for Coronavirus dataset took 0.5283622741699219s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3159.2220146656036s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.1568968296051025s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021083831787109375s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 5.936622619628906e-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 9.298324584960938e-06s
INFO | --- Analysis for micro-coronavirus took 3401.282647371292s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.76837158203125e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0003254413604736328s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.28392982482910156s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020072460174560547s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010418891906738281s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 8.25191879272461s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 7.843971252441406e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.28306102752685547s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02086639404296875s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010728836059570312s
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 5.9169228076934814s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.11375093460083008s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2638123035430908s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020704269409179688s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 6.985664367675781e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.867813110351562e-06s
INFO | --- Analysis for mlsa took 4.429794073104858s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.315376281738281e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.28624439239501953s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.7670135498046875e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 7.867813110351562e-06s
INFO | --- Analysis for model took 42.49686050415039s
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.172325134277344e-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.0006365776062011719s
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.2938525676727295s
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.02020859718322754s
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.775161743164062e-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.0007174015045166016s
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 4.744529724121094e-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.867813110351562e-06s
INFO | --- Analysis for model1 took 18.682965517044067s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.7206878662109375e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.27083492279052734s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020345449447631836s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.86102294921875e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 7.62939453125e-06s
INFO | --- Analysis for mond took 4.944374322891235s
Availability | SPARQL endpoint availability check for MONDIS took 4.100799560546875e-05s
Availability | VoID file availability check for MONDIS took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for MONDIS took 0.2828054428100586s
Reputation | Calculation of the PageRank for MONDIS took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for MONDIS took 6.270408630371094e-05s
Believability | Calculation of trust value for MONDIS took 1.33514404296875e-05s
INFO | --- Analysis for mondis took 3.152989625930786s
Availability | SPARQL endpoint availability check for Monumentos took 4.1484832763671875e-05s
Availability | VoID file availability check for Monumentos took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Monumentos took 0.2892897129058838s
Reputation | Calculation of the PageRank for Monumentos took 0.020786762237548828s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0008497238159179688s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.647804260253906e-05s
Believability | Calculation of trust value for Monumentos took 9.059906005859375e-06s
INFO | --- Analysis for monumentos-zaragoza took 3.143141746520996s
Availability | SPARQL endpoint availability check for MORElab took 0.9534478187561035s
Availability | VoID file availability check for MORElab took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for MORElab took 0.275371789932251s
Reputation | Calculation of the PageRank for MORElab took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for MORElab took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.940696716308594e-05s
Believability | Calculation of trust value for MORElab took 6.67572021484375e-06s
INFO | --- Analysis for morelab took 5.029123544692993s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.082263231277466s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.3024563789367676s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.749961853027344e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 6.4373016357421875e-06s
INFO | --- Analysis for msc took 6.681055307388306s
Availability | SPARQL endpoint availability check for Multext-East took 6.389617919921875e-05s
Availability | VoID file availability check for Multext-East took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for Multext-East took 0.28511738777160645s
Reputation | Calculation of the PageRank for Multext-East took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.552436828613281e-05s
Believability | Calculation of trust value for Multext-East took 7.152557373046875e-06s
INFO | --- Analysis for multext-east took 2.533609628677368s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.100799560546875e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.26962733268737793s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020304203033447266s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.0994415283203125e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 8.106231689453125e-06s
INFO | --- Analysis for multilingualeulaw took 3.594496011734009s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.9591064453125e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.27747106552124023s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.4809112548828125e-05s
Believability | Calculation of trust value for Multimedia Lab took 7.3909759521484375e-06s
INFO | --- Analysis for multimedia-lab took 3.023481845855713s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.1961669921875e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.27695155143737793s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.147125244140625e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 8.106231689453125e-06s
INFO | --- Analysis for munich-offener-haushalt took 3.0985653400421143s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.904325008392334s
Availability | VoID file availability check for Muninn World War I took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.28481388092041016s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 7.915496826171875e-05s
Believability | Calculation of trust value for Muninn World War I took 8.58306884765625e-06s
INFO | --- Analysis for muninn-world-war-i took 10.886802673339844s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.124641418457031e-05s
Availability | VoID file availability check for Musei Italiani took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.26947855949401855s
Reputation | Calculation of the PageRank for Musei Italiani took 0.02219104766845703s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.3855438232421875e-05s
Believability | Calculation of trust value for Musei Italiani took 8.106231689453125e-06s
INFO | --- Analysis for musei-italiani took 3.0828990936279297s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.482269287109375e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2926516532897949s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020835399627685547s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011134147644042969s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for museosespania-gnoss took 75.18262076377869s
Availability | SPARQL endpoint availability check for Italian Museums took 2.225440263748169s
Availability | VoID file availability check for Italian Museums took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.28707146644592285s
Reputation | Calculation of the PageRank for Italian Museums took 0.02134537696838379s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 0.00010585784912109375s
Believability | Calculation of trust value for Italian Museums took 1.1920928955078125e-05s
INFO | --- Analysis for museums-in-italy took 5.732699155807495s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.4345855712890625e-05s
Availability | VoID file availability check for MusicBrainz took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2774219512939453s
Reputation | Calculation of the PageRank for MusicBrainz took 0.021449565887451172s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 4.1961669921875e-05s
Believability | Calculation of trust value for MusicBrainz took 1.2636184692382812e-05s
INFO | --- Analysis for musicbrainz_ took 3.0853030681610107s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.482269287109375e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0003895759582519531s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.2715878486633301s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.024373292922973633s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0010225772857666016s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 4.076957702636719e-05s
Believability | Calculation of trust value for MusicNet Codex took 1.0251998901367188e-05s
INFO | --- Analysis for musicnet_codex took 3.6490728855133057s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7616574764251709s
Availability | VoID file availability check for Muziekweb took 0.0009667873382568359s
Extra | Recovery of all triples for Muziekweb took 1.9413104057312012s
Performance | Total latancy measurement for Muziekweb took 1.5056445598602295s
Amount of data | Number of triples check for Muziekweb took 0.3627746105194092s
Interoperability | New terms check for Muziekweb took 2.072943687438965s
Versatility | Languages check for Muziekweb took 57.82558274269104s
Interpretability | Number of blank nodes check for Muziekweb took 0.3309183120727539s
Interpretability | RDF structures check for Muziekweb took 0.86692214012146s
Versatility | Serialization formats check for Muziekweb took 0.35872840881347656s
Availability | RDF dump link check for Muziekweb took 0.27973198890686035s
License | MR license check for Muziekweb took 0.30850863456726074s
License | HR license check for Muziekweb took 13.139547348022461s
Amount of data | Number of property check for Muziekweb took 0.27114415168762207s
Understandability | Number of label check for Muziekweb took 0.37480831146240234s
Understandability | URI regex check for Muziekweb took 0.6215181350708008s
Understandability | Vocabs check for Muziekweb took 0.2986438274383545s
Verifiability | Authors check for Muziekweb took 0.27695775032043457s
Verifiability | Publishers check for Muziekweb took 0.29762697219848633s
Performance | Throughput check for Muziekweb took 11.709844589233398s
Amount of data | Check the number of entities for Muziekweb took 3.218650817871094e-05s
Verifiability | Contribs. check for Muziekweb took 0.3125157356262207s
Interlinking | sameAs chians check for Muziekweb took 0.3808777332305908s
Interlinking | skos check for Muziekweb took 0.3798656463623047s
Interlinking | skos check for Muziekweb took 0.3150172233581543s
Timeliness | dataset update frequency check for Muziekweb took 0.3067758083343506s
Currency | Creation date check for Muziekweb took 0.7709951400756836s
Currency | Modification date check for Muziekweb took 0.8666234016418457s
Rep.Conc. | URIs length for Muziekweb took 2.002591371536255s
Interoperability | New vocabularies check for Muziekweb took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.2741701602935791s
Accuracy | Check Functional Property for Muziekweb took 0.509202241897583s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.4815061092376709s
Accuracy | Check Empty annotation labels for Muziekweb took 0.9694569110870361s
Accuracy | Check White space in annotation for Muziekweb took 0.02874469757080078s
Accuracy | Check Datatype consistency for Muziekweb took 0.034913063049316406s
Consistency | Disjoint class check for Muziekweb took 0.5627896785736084s
Consistency | Check Misplaced properties for Muziekweb took 1.1688041687011719s
Consistency | Check Ontology hijacking for Muziekweb took 2.6105353832244873s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 2.594514846801758s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 2.064267158508301s
Conciseness | Check Extensional conciseness for Muziekweb took 0.042948007583618164s
Conciseness | Check Intensional conciseness for Muziekweb took 0.2781796455383301s
Security | Sign check for Muziekweb took 0.30268239974975586s
Availability | Check URIs Dereferenciability for Muziekweb took 1762.2590708732605s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.4485647678375244s
Reputation | Calculation of the PageRank for Muziekweb took 0.02123117446899414s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 2.1457672119140625e-06s
Believability | Calculation of trust value for Muziekweb took 8.58306884765625e-06s
INFO | --- Analysis for muziekweb took 1899.0395567417145s
Availability | SPARQL endpoint availability check for myExperiment took 0.3639957904815674s
Availability | VoID file availability check for myExperiment took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for myExperiment took 0.7400412559509277s
Reputation | Calculation of the PageRank for myExperiment took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.0001010894775390625s
Believability | Calculation of trust value for myExperiment took 1.0728836059570312e-05s
INFO | --- Analysis for my-experiment took 5.190497398376465s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.06948137283325195s
Availability | VoID file availability check for My Family Lineage took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.28580665588378906s
Reputation | Calculation of the PageRank for My Family Lineage took 0.022083520889282227s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.797645568847656e-05s
Believability | Calculation of trust value for My Family Lineage took 7.62939453125e-06s
INFO | --- Analysis for my-family-lineage took 5.071294069290161s
Availability | SPARQL endpoint availability check for My ontology test took 0.49912166595458984s
Availability | VoID file availability check for My ontology test took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for My ontology test took 0.2878754138946533s
Reputation | Calculation of the PageRank for My ontology test took 0.021502017974853516s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for My ontology test took 4.00543212890625e-05s
Believability | Calculation of trust value for My ontology test took 8.106231689453125e-06s
INFO | --- Analysis for myontologytest took 5.011984825134277s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.291534423828125e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.29103994369506836s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.021715641021728516s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.000118255615234375s
Believability | Calculation of trust value for myopenlink dataspaces took 8.106231689453125e-06s
INFO | --- Analysis for myopenlink-dataspaces took 3.8743321895599365s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.538853406906128s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.2826261520385742s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.021623849868774414s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 8.845329284667969e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for n-lex-as-linked-data took 11.607719421386719s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.64966130256653s
Availability | VoID file availability check for NAICS 2007 took 0.0008409023284912109s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.30951905250549316s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.021429061889648438s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0010335445404052734s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.601478576660156e-05s
Believability | Calculation of trust value for NAICS 2007 took 5.4836273193359375e-06s
INFO | --- Analysis for naics-2007 took 127.98175716400146s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.45475459098816s
Availability | VoID file availability check for NAICS 2012 took 0.0008764266967773438s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.28322386741638184s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020900726318359375s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.412101745605469e-05s
Believability | Calculation of trust value for NAICS 2012 took 2.2411346435546875e-05s
INFO | --- Analysis for naics-2012 took 125.72238564491272s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.2791867256164551s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.626678466796875e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 9.775161743164062e-06s
INFO | --- Analysis for nalt took 3.587716579437256s
Availability | SPARQL endpoint availability check for Usernames  took 4.172325134277344e-05s
Availability | VoID file availability check for Usernames  took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Usernames  took 0.7323827743530273s
Reputation | Calculation of the PageRank for Usernames  took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.0517578125e-05s
Believability | Calculation of trust value for Usernames  took 6.67572021484375e-06s
INFO | --- Analysis for Names took 4.005917310714722s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 4.1961669921875e-05s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.282656192779541s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 5.745887756347656e-05s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 8.106231689453125e-06s
INFO | --- Analysis for national-diet-library-authorities took 3.1015706062316895s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 4.172325134277344e-05s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.2727234363555908s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.078315734863281e-05s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 6.9141387939453125e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 3.5007236003875732s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.9570746421813965s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.2775897979736328s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007135868072509766s
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 8.106231689453125e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 4.994706869125366s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.076957702636719e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.29027485847473145s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.009506225585938e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.9141387939453125e-06s
INFO | --- Analysis for Naturopathy took 3.1080336570739746s
Availability | SPARQL endpoint availability check for Naturopathy took 4.76837158203125e-05s
Availability | VoID file availability check for Naturopathy took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.28408122062683105s
Reputation | Calculation of the PageRank for Naturopathy took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.2901763916015625e-05s
Believability | Calculation of trust value for Naturopathy took 8.821487426757812e-06s
INFO | --- Analysis for naturopathy2 took 3.496121644973755s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.2796895503997803s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.1948089599609375e-05s
Believability | Calculation of trust value for NCI Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for nci-thesaurus took 3.074552536010742s
Availability | SPARQL endpoint availability check for COVID-19 Data took 5.3882598876953125e-05s
Availability | VoID file availability check for COVID-19 Data took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.27445507049560547s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020664453506469727s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for COVID-19 Data took 8.58306884765625e-06s
INFO | --- Analysis for NCMI-COVID-19 took 3.085411787033081s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 4.100799560546875e-05s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.28450775146484375s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2159347534179688e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 2.288818359375e-05s
INFO | --- Analysis for NCMICOVID-19 took 3.0399057865142822s
Availability | SPARQL endpoint availability check for NDF-RT took 4.00543212890625e-05s
Availability | VoID file availability check for NDF-RT took 0.000217437744140625s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.2672433853149414s
Reputation | Calculation of the PageRank for NDF-RT took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.266334533691406e-05s
Believability | Calculation of trust value for NDF-RT took 9.059906005859375e-06s
INFO | --- Analysis for ndf-rt took 3.051872968673706s
Availability | SPARQL endpoint availability check for Near took 4.506111145019531e-05s
Availability | VoID file availability check for Near took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Near took 0.2850682735443115s
Reputation | Calculation of the PageRank for Near took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for Near took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Near took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Near took 9.083747863769531e-05s
Believability | Calculation of trust value for Near took 8.344650268554688e-06s
INFO | --- Analysis for near took 3.0655181407928467s
Availability | SPARQL endpoint availability check for Neel took 4.100799560546875e-05s
Availability | VoID file availability check for Neel took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Neel took 0.27933645248413086s
Reputation | Calculation of the PageRank for Neel took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for Neel took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neel took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Neel took 3.7670135498046875e-05s
Believability | Calculation of trust value for Neel took 1.0967254638671875e-05s
INFO | --- Analysis for neel took 3.070441961288452s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 3.910064697265625e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.27687525749206543s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 2.956390380859375e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 6.9141387939453125e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 3.0888445377349854s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 3.9577484130859375e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0002193450927734375s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2941594123840332s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.956390380859375e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 6.198883056640625e-06s
INFO | --- Analysis for neurolex-wiki took 3.05409574508667s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.00543212890625e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2798647880554199s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.57763671875e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 6.4373016357421875e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.085820436477661s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.100799560546875e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.27242493629455566s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.818771362304688e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 6.67572021484375e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 3.0643904209136963s
Availability | SPARQL endpoint availability check for Newsweek took 4.2438507080078125e-05s
Availability | VoID file availability check for Newsweek took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Newsweek took 0.7248244285583496s
Reputation | Calculation of the PageRank for Newsweek took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.0517578125e-05s
Believability | Calculation of trust value for Newsweek took 5.9604644775390625e-06s
INFO | --- Analysis for newsweek took 3.5030152797698975s
Availability | SPARQL endpoint availability check for neXtProt took 4.00543212890625e-05s
Availability | VoID file availability check for neXtProt took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2845282554626465s
Reputation | Calculation of the PageRank for neXtProt took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.910064697265625e-05s
Believability | Calculation of trust value for neXtProt took 6.67572021484375e-06s
INFO | --- Analysis for nextprot took 3.0774459838867188s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.458427429199219e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.28478217124938965s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02100992202758789s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010848045349121094s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.33514404296875e-05s
INFO | --- Analysis for nextweb-gnoss took 3.087327480316162s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.0531158447265625e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.2802293300628662s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020723342895507812s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.654594421386719e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 8.344650268554688e-06s
INFO | --- Analysis for nhs-jargon took 3.0857183933258057s
Availability | SPARQL endpoint availability check for NIT Patna took 4.673004150390625e-05s
Availability | VoID file availability check for NIT Patna took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.2914559841156006s
Reputation | Calculation of the PageRank for NIT Patna took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 7.724761962890625e-05s
Believability | Calculation of trust value for NIT Patna took 7.3909759521484375e-06s
INFO | --- Analysis for NITP took 3.15290904045105s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.124641418457031e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.28936100006103516s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020585298538208008s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.600120544433594e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 7.152557373046875e-06s
INFO | --- Analysis for nlm_2007_mesh took 3.0467684268951416s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2789478302001953s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 8.344650268554688e-06s
INFO | --- Analysis for nlr-dataset-mod took 3.08603835105896s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 4.315376281738281e-05s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.00039315223693847656s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2645444869995117s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 7.62939453125e-06s
INFO | --- Analysis for NLW took 3.049882173538208s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.981590270996094e-05s
Availability | VoID file availability check for Nobel Prizes took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.2791938781738281s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 0.00010085105895996094s
Believability | Calculation of trust value for Nobel Prizes took 7.152557373046875e-06s
INFO | --- Analysis for nobelprizes took 3.051384210586548s
Availability | SPARQL endpoint availability check for NoiPA took 4.100799560546875e-05s
Availability | VoID file availability check for NoiPA took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for NoiPA took 0.2728312015533447s
Reputation | Calculation of the PageRank for NoiPA took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.0279159545898438e-05s
Believability | Calculation of trust value for NoiPA took 5.9604644775390625e-06s
INFO | --- Analysis for NoiPA took 3.044368267059326s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.36478328704834s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.27927398681640625s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020186424255371094s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 0.00010776519775390625s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.867813110351562e-06s
INFO | --- Analysis for nom took 12.048620462417603s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 4.7206878662109375e-05s
Availability | VoID file availability check for Nomenclator Asturias took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.27263641357421875s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.225440979003906e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 9.059906005859375e-06s
INFO | --- Analysis for nomenclator-asturias took 3.0515151023864746s
Availability | SPARQL endpoint availability check for nomisma took 4.1961669921875e-05s
Availability | VoID file availability check for nomisma took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for nomisma took 0.27879977226257324s
Reputation | Calculation of the PageRank for nomisma took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for nomisma took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.0279159545898438e-05s
Believability | Calculation of trust value for nomisma took 7.152557373046875e-06s
INFO | --- Analysis for nomisma took 3.055508613586426s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.5642399787902832s
Availability | VoID file availability check for Nomisma.org  took 0.0002715587615966797s
Extra | Recovery of all triples for Nomisma.org  took 300.0081236362457s
Performance | Total latancy measurement for Nomisma.org  took 2.417221784591675s
Amount of data | Number of triples check for Nomisma.org  took 39.539706230163574s
Interoperability | New terms check for Nomisma.org  took 9.271032810211182s
Versatility | Languages check for Nomisma.org  took 137.4081587791443s
Interpretability | Number of blank nodes check for Nomisma.org  took 42.86419129371643s
Security | Check HTTPS for Nomisma.org  took 1.0401692390441895s
Interpretability | RDF structures check for Nomisma.org  took 0.5127208232879639s
Versatility | Serialization formats check for Nomisma.org  took 0.4831080436706543s
Availability | RDF dump link check for Nomisma.org  took 1251.4579770565033s
License | MR license check for Nomisma.org  took 0.5384738445281982s
License | HR license check for Nomisma.org  took 61.01865839958191s
Amount of data | Number of property check for Nomisma.org  took 0.8299200534820557s
Understandability | Number of label check for Nomisma.org  took 7.322153091430664s
Understandability | URI regex check for Nomisma.org  took 1.0331342220306396s
Understandability | Vocabs check for Nomisma.org  took 1.1223347187042236s
Verifiability | Authors check for Nomisma.org  took 0.5887055397033691s
Verifiability | Publishers check for Nomisma.org  took 0.46378159523010254s
Performance | Throughput check for Nomisma.org  took 12.62230134010315s
Amount of data | Check the number of entities for Nomisma.org  took 0.0004210472106933594s
Verifiability | Contribs. check for Nomisma.org  took 0.4923105239868164s
Interlinking | sameAs chians check for Nomisma.org  took 0.488633394241333s
Interlinking | skos check for Nomisma.org  took 1.2490243911743164s
Interlinking | skos check for Nomisma.org  took 1.1711742877960205s
Timeliness | dataset update frequency check for Nomisma.org  took 0.4343123435974121s
Currency | Creation date check for Nomisma.org  took 1.035182237625122s
Currency | Modification date check for Nomisma.org  took 0.4528937339782715s
Rep.Conc. | URIs length for Nomisma.org  took 334.6352334022522s
Interoperability | New vocabularies check for Nomisma.org  took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 15.460670471191406s
Accuracy | Check Functional Property for Nomisma.org  took 0.5419588088989258s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 1.8829076290130615s
Consistency | Disjoint class check for Nomisma.org  took 0.47223925590515137s
Consistency | Check Misplaced properties for Nomisma.org  took 27.01643657684326s
Consistency | Check Ontology hijacking for Nomisma.org  took 434.3349275588989s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 53.34421133995056s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00017189979553222656s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.9132788181304932s
Security | Sign check for Nomisma.org  took 0.9987549781799316s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.291799545288086s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.02093362808227539s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 2.1457672119140625e-06s
Believability | Calculation of trust value for Nomisma.org  took 8.344650268554688e-06s
INFO | --- Analysis for nomisma_org took 8467.38876748085s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.8323302268981934s
Availability | VoID file availability check for Curriculum Vitae took 0.00029087066650390625s
Extra | Recovery of all triples for Curriculum Vitae took 0.7414016723632812s
Performance | Total latancy measurement for Curriculum Vitae took 1.0300970077514648s
Amount of data | Number of triples check for Curriculum Vitae took 0.2136554718017578s
Interoperability | New terms check for Curriculum Vitae took 1.405360221862793s
Versatility | Languages check for Curriculum Vitae took 0.641533374786377s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.20654988288879395s
Interpretability | RDF structures check for Curriculum Vitae took 0.21236085891723633s
Versatility | Serialization formats check for Curriculum Vitae took 0.20872259140014648s
Availability | RDF dump link check for Curriculum Vitae took 0.20124602317810059s
License | MR license check for Curriculum Vitae took 0.22133755683898926s
License | HR license check for Curriculum Vitae took 0.21258187294006348s
Amount of data | Number of property check for Curriculum Vitae took 0.22004199028015137s
Understandability | Number of label check for Curriculum Vitae took 0.22587132453918457s
Understandability | URI regex check for Curriculum Vitae took 0.439896821975708s
Understandability | Vocabs check for Curriculum Vitae took 0.20592308044433594s
Verifiability | Authors check for Curriculum Vitae took 0.20497465133666992s
Verifiability | Publishers check for Curriculum Vitae took 0.2282567024230957s
Performance | Throughput check for Curriculum Vitae took 10.461966037750244s
Amount of data | Check the number of entities for Curriculum Vitae took 7.152557373046875e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.20910954475402832s
Interlinking | sameAs chians check for Curriculum Vitae took 0.19989943504333496s
Interlinking | skos check for Curriculum Vitae took 0.2058713436126709s
Interlinking | skos check for Curriculum Vitae took 0.20183229446411133s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.20991730690002441s
Currency | Creation date check for Curriculum Vitae took 0.4222235679626465s
Currency | Modification date check for Curriculum Vitae took 0.4070584774017334s
Rep.Conc. | URIs length for Curriculum Vitae took 0.5536518096923828s
Interoperability | New vocabularies check for Curriculum Vitae took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.21335935592651367s
Accuracy | Check Functional Property for Curriculum Vitae took 0.19874286651611328s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.20640277862548828s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.20676255226135254s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00010609626770019531s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.003420114517211914s
Consistency | Disjoint class check for Curriculum Vitae took 0.20978879928588867s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.6131587028503418s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.4095494747161865s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.1680409908294678s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.381653070449829s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0013010501861572266s
Security | Sign check for Curriculum Vitae took 0.21867823600769043s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 22.036300897598267s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.26711440086364746s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.02158212661743164s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.9073486328125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 6.198883056640625e-06s
INFO | --- Analysis for Nordine_Bittich took 65.66507077217102s
Availability | SPARQL endpoint availability check for NorPark took 2.1254963874816895s
Availability | VoID file availability check for NorPark took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for NorPark took 0.2684154510498047s
Reputation | Calculation of the PageRank for NorPark took 0.020435810089111328s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for NorPark took 6.961822509765625e-05s
Believability | Calculation of trust value for NorPark took 8.106231689453125e-06s
INFO | --- Analysis for norpark took 5.141663074493408s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.0240933895111084s
Availability | VoID file availability check for Parking Dataset took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2670280933380127s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020138025283813477s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for Parking Dataset took 8.58306884765625e-06s
INFO | --- Analysis for norpark2 took 3.8191850185394287s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 354.4647390842438s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.2632451057434082s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0009720325469970703s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 7.3909759521484375e-06s
INFO | --- Analysis for Norway_Fishery_ took 629.4819643497467s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.40473198890686035s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0013089179992675781s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.6889727115631104s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.2239234447479248s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.001125335693359375s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 9.5367431640625e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 8.106231689453125e-06s
INFO | --- Analysis for norwegian-geo-divisions took 9.23523235321045s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.410743713378906e-05s
Availability | VoID file availability check for NorwegianSoE took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.26816511154174805s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.043184757232666016s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0016379356384277344s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 5.91278076171875e-05s
Believability | Calculation of trust value for NorwegianSoE took 1.1682510375976562e-05s
INFO | --- Analysis for norwegiansoe took 4.761196136474609s
Availability | SPARQL endpoint availability check for NITP took 6.818771362304688e-05s
Availability | VoID file availability check for NITP took 0.0008556842803955078s
Completeness | Calculation of interlinking completeness for NITP took 0.7031033039093018s
Reputation | Calculation of the PageRank for NITP took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for NITP took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for NITP took 7.414817810058594e-05s
Believability | Calculation of trust value for NITP took 8.344650268554688e-06s
INFO | --- Analysis for notIdentifier took 4.919455528259277s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.673004150390625e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.26572751998901367s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.021240234375s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.886222839355469e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.3113021850585938e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.8504278659820557s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.4345855712890625e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2704150676727295s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.021148681640625s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.719329833984375e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 9.5367431640625e-06s
INFO | --- Analysis for npg took 3.9261579513549805s
Availability | SPARQL endpoint availability check for NPM took 4.601478576660156e-05s
Availability | VoID file availability check for NPM took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for NPM took 0.26363182067871094s
Reputation | Calculation of the PageRank for NPM took 0.020969867706298828s
Interlinking | Calculation of Degree of Connection for NPM took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for NPM took 3.5762786865234375e-05s
Believability | Calculation of trust value for NPM took 1.1444091796875e-05s
INFO | --- Analysis for npm took 3.814484119415283s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.04930901527404785s
Availability | VoID file availability check for NTNU special collections took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.26143479347229004s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 6.079673767089844e-05s
Believability | Calculation of trust value for NTNU special collections took 8.821487426757812e-06s
INFO | --- Analysis for ntnusc took 5.5384697914123535s
Availability | SPARQL endpoint availability check for links took 5.412101745605469e-05s
Availability | VoID file availability check for links took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for links took 0.2557072639465332s
Reputation | Calculation of the PageRank for links took 0.021524429321289062s
Interlinking | Calculation of Degree of Connection for links took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for links took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for links took 1.4781951904296875e-05s
Believability | Calculation of trust value for links took 1.0013580322265625e-05s
INFO | --- Analysis for nugmyanmar took 2.7547953128814697s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.6253204345703125e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2620201110839844s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.06389760971069336s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00011992454528808594s
Believability | Calculation of trust value for NUTS (GeoVocab) took 1.049041748046875e-05s
INFO | --- Analysis for nuts-geovocab took 6.154772996902466s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.3970627784729004s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.2622842788696289s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.02141880989074707s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 8.130073547363281e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.3113021850585938e-05s
INFO | --- Analysis for nvd took 4.362433195114136s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 1.1725695133209229s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.00032806396484375s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.268002986907959s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.021833181381225586s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0009486675262451172s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 0.00011110305786132812s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 8.106231689453125e-06s
INFO | --- Analysis for nvs took 9.080980062484741s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.458427429199219e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.26662635803222656s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020906686782836914s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0008623600006103516s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0002243518829345703s
Believability | Calculation of trust value for New York Times - Linked Open Data took 9.059906005859375e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.4329674243927s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.029273986816406e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.2604410648345947s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.02117013931274414s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0011169910430908203s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 4.291534423828125e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 8.106231689453125e-06s
INFO | --- Analysis for o-anc took 2.979083776473999s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.363059997558594e-05s
Availability | VoID file availability check for OANetzwerk took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.27237892150878906s
Reputation | Calculation of the PageRank for OANetzwerk took 0.027539968490600586s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0015568733215332031s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 5.984306335449219e-05s
Believability | Calculation of trust value for OANetzwerk took 1.2874603271484375e-05s
INFO | --- Analysis for oanetzwerk took 2.9382121562957764s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 5.650520324707031e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.2640037536621094s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.027850866317749023s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0011954307556152344s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 4.1484832763671875e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 9.5367431640625e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.963545560836792s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.5322892665863037s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.00047707557678222656s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 3.6276602745056152s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.5158023834228516s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.6217117309570312s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 9.916128873825073s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.27371311187744s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.9191808700561523s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.22777676582336426s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.32433390617370605s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.4510982036590576s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.4015214443206787s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.5493977069854736s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.29794645309448s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.2978177070617676s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.8263590335845947s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.5577819347381592s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.3996398448944092s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.3756735324859619s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3578026294708252s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 12.860044479370117s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 8.130073547363281e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.3382530212402344s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.3072497844696045s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3366255760192871s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.40687990188598633s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.3847026824951172s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6573686599731445s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.33156824111938477s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 18.474864721298218s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.28582763671875s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.28438687324523926s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.3271169662475586s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 1.469900131225586s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.023730754852294922s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.028780460357666016s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.30063533782958984s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.584739208221436s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.38135647773742676s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.293060064315796s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.1535592079162598s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 16.947113037109375s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.06301188468933105s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.32350707054138184s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.2954390048980713s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 11.824151515960693s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.37188076972961426s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.822845458984375e-05s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 5.9604644775390625e-06s
INFO | --- Analysis for ocd took 393.8122088909149s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.315376281738281e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.26645517349243164s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020145654678344727s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.8623809814453125e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-borehole took 3.1065311431884766s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.2343096733093262s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2713627815246582s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.559226989746094e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 6.4373016357421875e-06s
INFO | --- Analysis for oceandrilling-codices took 6.800195693969727s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.0528807640075684s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.00040435791015625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.28073716163635254s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.123283386230469e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 5.673053503036499s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.0570662021636963s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2567896842956543s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.409385681152344e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 5.9604644775390625e-06s
INFO | --- Analysis for oceandrilling-forams took 6.233513116836548s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.0480375289916992s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.26117372512817383s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02120041847229004s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 4.124641418457031e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-janus took 6.323859214782715s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 11.0732581615448s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.25884270668029785s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 8.344650268554688e-06s
INFO | --- Analysis for oceandrilling-janusamp took 15.551841259002686s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1167302131652832s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.26316022872924805s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.9087066650390625e-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.633221864700317s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 5.507469177246094e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2642533779144287s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.91278076171875e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 8.58306884765625e-06s
INFO | --- Analysis for oclc-fast took 6.327198028564453s
Availability | SPARQL endpoint availability check for Open Data Communities took 5.459785461425781e-05s
Availability | VoID file availability check for Open Data Communities took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2596125602722168s
Reputation | Calculation of the PageRank for Open Data Communities took 0.02093362808227539s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 4.00543212890625e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.001055002212524414s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 4.100799560546875e-05s
Believability | Calculation of trust value for Open Data Communities took 8.344650268554688e-06s
INFO | --- Analysis for odc took 2.890131711959839s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.38690185546875e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.7016668319702148s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.100799560546875e-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 3.5409531593322754s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.0531158447265625e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2599320411682129s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020151853561401367s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 7.867813110351562e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 3.3433308601379395s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.16118812561035156s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.25559544563293457s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.021123647689819336s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0009226799011230469s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 8.440017700195312e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.0067901611328125e-06s
INFO | --- Analysis for odc-lsoa took 3.251943349838257s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.1961669921875e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2692990303039551s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.8133392333984375e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 7.62939453125e-06s
INFO | --- Analysis for odc-population-2005 took 2.930708885192871s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.076957702636719e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.27441930770874023s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.6702880859375e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 6.67572021484375e-06s
INFO | --- Analysis for ods took 2.885322332382202s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.4030320644378662s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0004172325134277344s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.262371301651001s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02019667625427246s
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.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.226799011230469e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for oecd-linked-data took 2.8078348636627197s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.1961669921875e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.2639615535736084s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.0279159545898438e-05s
Believability | Calculation of trust value for Offener Haushalt took 6.9141387939453125e-06s
INFO | --- Analysis for offener-haushalt took 2.8604440689086914s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.15229892730713s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.26296091079711914s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020784616470336914s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.3392181396484375e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 7.867813110351562e-06s
INFO | --- Analysis for ogolod took 103.06235527992249s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.3392181396484375e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.2647831439971924s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.647804260253906e-05s
Believability | Calculation of trust value for OLAC Metadata took 7.3909759521484375e-06s
INFO | --- Analysis for olac took 22.6166353225708s
Availability | SPARQL endpoint availability check for OLiA took 7.343292236328125e-05s
Availability | VoID file availability check for OLiA took 0.0007860660552978516s
Completeness | Calculation of interlinking completeness for OLiA took 0.306168794631958s
Reputation | Calculation of the PageRank for OLiA took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for OLiA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.0001239776611328125s
Believability | Calculation of trust value for OLiA took 8.106231689453125e-06s
INFO | --- Analysis for olia took 12.589778661727905s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.506111145019531e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0009558200836181641s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2631113529205322s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020180702209472656s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 7.081031799316406e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.0728836059570312e-05s
INFO | --- Analysis for olia-discourse took 7.427669286727905s
Availability | SPARQL endpoint availability check for Open Land Use took 393.1401958465576s
Availability | VoID file availability check for Open Land Use took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.6974928379058838s
Reputation | Calculation of the PageRank for Open Land Use took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.3392181396484375e-05s
Believability | Calculation of trust value for Open Land Use took 7.62939453125e-06s
INFO | --- Analysis for OLU took 668.0849351882935s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.696846008300781e-05s
Availability | VoID file availability check for OmegaWiki took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for OmegaWiki took 1.1554670333862305s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.8133392333984375e-05s
Believability | Calculation of trust value for OmegaWiki took 1.2874603271484375e-05s
INFO | --- Analysis for omegawiki took 6.469748020172119s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.6674742698669434s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.26745176315307617s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0008404254913330078s
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 7.3909759521484375e-06s
INFO | --- Analysis for omwn-als took 4.9492034912109375s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.29465222358703613s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2662684917449951s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020062923431396484s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-arb took 4.4564738273620605s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.30495691299438477s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.6979153156280518s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-bul took 3.54225492477417s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2799832820892334s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2550210952758789s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-cow took 3.8870866298675537s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.29412126541137695s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2649850845336914s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-cwn took 3.473789930343628s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2398388385772705s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2697927951812744s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 6.4373016357421875e-06s
INFO | --- Analysis for omwn-dan took 3.399035930633545s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.24207329750061035s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0003628730773925781s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2659897804260254s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.021122455596923828s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-ell took 3.0174405574798584s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2502305507659912s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2627432346343994s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-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 3.138413429260254s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 1.2725813388824463s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.25868725776672363s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02024555206298828s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-fas took 4.561466693878174s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2998225688934326s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2631556987762451s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02020573616027832s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-fin took 3.0923686027526855s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2583465576171875s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.26940035820007324s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020189285278320312s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-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 3.552436828613281e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-fra took 3.080057382583618s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.23029518127441406s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.26911139488220215s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-heb took 3.1058390140533447s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2662389278411865s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.26477813720703125s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-hrv took 3.44415283203125s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.261871337890625s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2590949535369873s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-isl took 2.9747426509857178s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.26102781295776367s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.26723814010620117s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-ita took 2.981624126434326s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2599751949310303s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.25962114334106445s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02018141746520996s
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.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-iwn took 3.024606704711914s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.3170499801635742s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.26691246032714844s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020207643508911133s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 5.9604644775390625e-06s
INFO | --- Analysis for omwn-jpn took 3.0844764709472656s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2686901092529297s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.25418591499328613s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020432710647583008s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 5.245208740234375e-06s
INFO | --- Analysis for omwn-mcr took 2.98282790184021s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.23966360092163086s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2651674747467041s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-msa took 2.9857490062713623s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.24678325653076172s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.267427921295166s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020190954208374023s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 5.9604644775390625e-06s
INFO | --- Analysis for omwn-nld took 3.007554769515991s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2532312870025635s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.26624155044555664s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020499229431152344s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-nor took 3.01216983795166s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2393653392791748s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.25762152671813965s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-pol took 2.987799644470215s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2472238540649414s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2661173343658447s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-por took 2.9948291778564453s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2628293037414551s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.25789785385131836s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-ron took 2.9872279167175293s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.25267887115478516s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.26032185554504395s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02031087875366211s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 5.817413330078125e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-slk took 2.997283935546875s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.23631668090820312s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.27008628845214844s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020155668258666992s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-slv took 3.0495712757110596s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.26658105850219727s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.27487897872924805s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-swe took 3.0262506008148193s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.2718501091003418s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2667875289916992s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.02013874053955078s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-tha took 3.049332618713379s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 5.036115884780884s
Availability | VoID file availability check for OntoBeef Domain took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2609591484069824s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.363059997558594e-05s
Believability | Calculation of trust value for OntoBeef Domain took 6.198883056640625e-06s
INFO | --- Analysis for ontobeef-domain took 32.60874342918396s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.315376281738281e-05s
Availability | VoID file availability check for Ontos News Portal took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2667200565338135s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.512901306152344e-05s
Believability | Calculation of trust value for Ontos News Portal took 6.67572021484375e-06s
INFO | --- Analysis for ontos-news-portal took 6.705700635910034s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.2438507080078125e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.2622227668762207s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 2.9087066650390625e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 6.9141387939453125e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.5084245204925537s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 0.0001308917999267578s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2611429691314697s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020290613174438477s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.504753112792969e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 17.642565727233887s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.26200008392333984s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020192861557006836s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.8371810913085938e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.913149356842041s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.291534423828125e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0008237361907958984s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.27405357360839844s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.025332212448120117s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0014386177062988281s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 9.417533874511719e-05s
Believability | Calculation of trust value for Open Data Euskadi took 7.867813110351562e-06s
INFO | --- Analysis for open-data-euskadi took 7.891857385635376s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 7.62939453125e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.27454066276550293s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.032030344009399414s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0018029212951660156s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.0002040863037109375s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.2159347534179688e-05s
INFO | --- Analysis for open-data-risp took 4.45831823348999s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.19844865798950195s
Availability | VoID file availability check for Open Data Thesaurus took 0.0009026527404785156s
Extra | Recovery of all triples for Open Data Thesaurus took 1.6886439323425293s
Performance | Total latancy measurement for Open Data Thesaurus took 0.475813627243042s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1174631118774414s
Interoperability | New terms check for Open Data Thesaurus took 1.8903539180755615s
Versatility | Languages check for Open Data Thesaurus took 0.11943793296813965s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.12295675277709961s
Security | Check HTTPS for Open Data Thesaurus took 0.3453993797302246s
Interpretability | RDF structures check for Open Data Thesaurus took 0.11680841445922852s
Versatility | Serialization formats check for Open Data Thesaurus took 0.1169443130493164s
Availability | RDF dump link check for Open Data Thesaurus took 1.1077158451080322s
License | MR license check for Open Data Thesaurus took 0.1172478199005127s
License | HR license check for Open Data Thesaurus took 0.09366798400878906s
Amount of data | Number of property check for Open Data Thesaurus took 0.1153261661529541s
Understandability | Number of label check for Open Data Thesaurus took 0.11861729621887207s
Understandability | URI regex check for Open Data Thesaurus took 0.18069934844970703s
Understandability | Vocabs check for Open Data Thesaurus took 0.1177985668182373s
Verifiability | Authors check for Open Data Thesaurus took 0.11813735961914062s
Verifiability | Publishers check for Open Data Thesaurus took 0.11687755584716797s
Performance | Throughput check for Open Data Thesaurus took 10.71618366241455s
Amount of data | Check the number of entities for Open Data Thesaurus took 4.9591064453125e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.11349296569824219s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.1138303279876709s
Interlinking | skos check for Open Data Thesaurus took 0.11720514297485352s
Interlinking | skos check for Open Data Thesaurus took 0.08963680267333984s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.08854889869689941s
Currency | Creation date check for Open Data Thesaurus took 0.18236184120178223s
Currency | Modification date check for Open Data Thesaurus took 0.20464277267456055s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4523003101348877s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.12573766708374023s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.0889427661895752s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08921074867248535s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.172224760055542s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011448860168457031s
Consistency | Disjoint class check for Open Data Thesaurus took 0.08967208862304688s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.18352770805358887s
Consistency | Misplaced classes for Open Data Thesaurus took 0.08962130546569824s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.6892414093017578s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.6095685958862305s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00021314620971679688s
Security | Sign check for Open Data Thesaurus took 0.09012699127197266s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.26281213760375977s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.225440979003906e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for open-data-thesaurus took 63.93804979324341s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.363059997558594e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.27140069007873535s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.02595353126525879s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0009875297546386719s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 4.887580871582031e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 1.1444091796875e-05s
INFO | --- Analysis for open-data-tor-vergata took 2.9455442428588867s
Availability | SPARQL endpoint availability check for Open Election Data Project took 5.9604644775390625e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.2710566520690918s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.021360158920288086s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 7.987022399902344e-05s
Believability | Calculation of trust value for Open Election Data Project took 5.0067901611328125e-06s
INFO | --- Analysis for open-election-data-project took 4.695502042770386s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.5755739212036133s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.26136207580566406s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.027703285217285156s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0013175010681152344s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.0001347064971923828s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 7.152557373046875e-06s
INFO | --- Analysis for open-energy-info-wiki took 12.758256673812866s
Availability | SPARQL endpoint availability check for Open Library took 5.14984130859375e-05s
Availability | VoID file availability check for Open Library took 0.00083160400390625s
Completeness | Calculation of interlinking completeness for Open Library took 0.2683241367340088s
Reputation | Calculation of the PageRank for Open Library took 0.023747682571411133s
Interlinking | Calculation of Degree of Connection for Open Library took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0013077259063720703s
Interlinking | Calculation of Clustering coefficient for Open Library took 9.799003601074219e-05s
Believability | Calculation of trust value for Open Library took 1.5735626220703125e-05s
INFO | --- Analysis for open-library took 34.3635733127594s
Availability | SPARQL endpoint availability check for Open Directory took 4.482269287109375e-05s
Availability | VoID file availability check for Open Directory took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2673146724700928s
Reputation | Calculation of the PageRank for Open Directory took 0.025785207748413086s
Interlinking | Calculation of Degree of Connection for Open Directory took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.001374959945678711s
Interlinking | Calculation of Clustering coefficient for Open Directory took 4.315376281738281e-05s
Believability | Calculation of trust value for Open Directory took 9.5367431640625e-06s
INFO | --- Analysis for open_directory took 2.9268345832824707s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 393.63497376441956s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.7024250030517578s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 3.4809112548828125e-05s
Believability | Calculation of trust value for Open Land Use @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Open_Land_Use took 670.6392233371735s
Availability | SPARQL endpoint availability check for flyatlas took 1.6357543468475342s
Availability | VoID file availability check for flyatlas took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for flyatlas took 0.2735745906829834s
Reputation | Calculation of the PageRank for flyatlas took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.9577484130859375e-05s
Believability | Calculation of trust value for flyatlas took 6.198883056640625e-06s
INFO | --- Analysis for openbiomed-flyatlas took 12.479037284851074s
Availability | SPARQL endpoint availability check for OpenCalais took 4.601478576660156e-05s
Availability | VoID file availability check for OpenCalais took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.7016992568969727s
Reputation | Calculation of the PageRank for OpenCalais took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010609626770019531s
Believability | Calculation of trust value for OpenCalais took 1.0251998901367188e-05s
INFO | --- Analysis for opencalais took 4.977491855621338s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.3392181396484375e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.000579833984375s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.2590980529785156s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.414817810058594e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 4.291534423828125e-06s
INFO | --- Analysis for opencorporates took 3.6056065559387207s
Availability | SPARQL endpoint availability check for OpenCyc took 4.291534423828125e-05s
Availability | VoID file availability check for OpenCyc took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2534956932067871s
Reputation | Calculation of the PageRank for OpenCyc took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010561943054199219s
Believability | Calculation of trust value for OpenCyc took 5.7220458984375e-06s
INFO | --- Analysis for opencyc took 2.8807122707366943s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.25967955589294434s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020811080932617188s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.528594970703125e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.3456006050109863s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0010728836059570312s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.6966722011566162s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.847322940826416s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 6.818771362304688e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.26459288597106934s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.461552143096924s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.9114227294921875e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.699359655380249s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 3.1940441131591797s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.25999021530151367s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.4595677852630615s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.27110958099365234s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.9393930435180664s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.25974488258361816s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.4329960346221924s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2593204975128174s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.021568775177001953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.267692565917969e-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.335106134414673s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 6.628036499023438e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.26584362983703613s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.5221211910247803s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.25368809700012207s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.4539546966552734s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.26298046112060547s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.4847049713134766s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.2629730701446533s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02105426788330078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.467494249343872s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.260239839553833s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.3842217922210693s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0003037452697753906s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.2552454471588135s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.322615385055542s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.26178979873657227s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.431169271469116s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2680528163909912s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.501295566558838s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.25424981117248535s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.059906005859375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.4958603382110596s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.744529724121094e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2549314498901367s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.4006192684173584s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2716646194458008s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020533084869384766s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.354109525680542s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2570621967315674s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.4216508865356445s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.24857544898986816s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.4056568145751953s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 6.532669067382812e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2668721675872803s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.41828989982605s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.2535853385925293s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.3467018604278564s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.26214170455932617s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 5.2928924560546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.389986276626587s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.26813697814941406s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.4715218544006348s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2622411251068115s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02061152458190918s
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.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.8570618629455566s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2561976909637451s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.468583106994629s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.258267879486084s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.4442031383514404s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.25687670707702637s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020663022994995117s
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.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.887580871582031e-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.3488504886627197s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.25558996200561523s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.3666751384735107s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0003628730773925781s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2574734687805176s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.172325134277344e-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.3644447326660156s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.26055002212524414s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.439589023590088s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.225440979003906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.260498046875s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.021207571029663086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 5.364418029785156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.4995298385620117s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2656424045562744s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.221366882324219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.329179048538208s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 7.510185241699219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0003113746643066406s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.25890636444091797s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.059906005859375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.3391387462615967s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2770531177520752s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02084827423095703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.5313029289245605s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2627749443054199s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.4585702419281006s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.25802135467529297s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02069711685180664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 3.886222839355469e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.4354512691497803s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.26277899742126465s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.430513381958008s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 7.414817810058594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2660183906555176s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.7206878662109375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.4971444606781006s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.26503634452819824s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.775161743164062e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.4873106479644775s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.26150059700012207s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.475836753845215s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 6.604194641113281e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2604677677154541s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02113485336303711s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.5013842582702637s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.196415185928345s
Availability | VoID file availability check for Open Data of Ecuador took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2617189884185791s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.368492126464844e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 8.58306884765625e-06s
INFO | --- Analysis for opendataec took 8.768900156021118s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2642049789428711s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.6332039833068848s
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.0006299018859863281s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.25806522369384766s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.4663503170013428s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.315376281738281e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2615964412689209s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.393000841140747s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2553720474243164s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.4104232788085938s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.2650430202484131s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02166271209716797s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0008978843688964844s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 5.3882598876953125e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.3755156993865967s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.553794860839844e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.25682711601257324s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.4004549980163574s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 7.2479248046875e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2638969421386719s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.3988637924194336s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.935264587402344e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2634437084197998s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.403780937194824s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.8160552978515625e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.26400089263916016s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 8.344650268554688e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.353480100631714s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.513358116149902s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00037741661071777344s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.27118659019470215s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.0994415283203125e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.0013580322265625e-05s
INFO | --- Analysis for openlink-lod-cache took 63.142335653305054s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.220008850097656e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.31107282638549805s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.655952453613281e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 7.867813110351562e-06s
INFO | --- Analysis for openlinksw-dataspaces took 5.194930076599121s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.410743713378906e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.3041541576385498s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.322166442871094e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 4.76837158203125e-06s
INFO | --- Analysis for openlylocal took 25.037110090255737s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.8249750137329102s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.6639420986175537s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.343292236328125e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 6.4373016357421875e-06s
INFO | --- Analysis for openmobilenetwork took 4.583862781524658s
Availability | SPARQL endpoint availability check for OpenTox took 4.100799560546875e-05s
Availability | VoID file availability check for OpenTox took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for OpenTox took 0.954949140548706s
Reputation | Calculation of the PageRank for OpenTox took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for OpenTox took 2.8848648071289062e-05s
Believability | Calculation of trust value for OpenTox took 6.67572021484375e-06s
INFO | --- Analysis for opentox took 5.046027183532715s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.4350306987762451s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for openuplabs took 4.618408441543579s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.076957702636719e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.3170456886291504s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.8133392333984375e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 6.9141387939453125e-06s
INFO | --- Analysis for opus took 4.668840408325195s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.0531158447265625e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.4138150215148926s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020177841186523438s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.838539123535156e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 6.67572021484375e-06s
INFO | --- Analysis for orcid took 4.230429172515869s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9990324974060059s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0008106231689453125s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.3071095943450928s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.5367431640625e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 7.62939453125e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.819519281387329s
Availability | SPARQL endpoint availability check for oreilly took 4.267692565917969e-05s
Availability | VoID file availability check for oreilly took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for oreilly took 0.3198854923248291s
Reputation | Calculation of the PageRank for oreilly took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for oreilly took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.935264587402344e-05s
Believability | Calculation of trust value for oreilly took 7.62939453125e-06s
INFO | --- Analysis for oreilly took 5.256064176559448s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.431286334991455s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.3113739490509033s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.4809112548828125e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 8.106231689453125e-06s
INFO | --- Analysis for Organchem-Data took 9.30185055732727s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.12653493881225586s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.32649707794189453s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.390975952148438e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for organic-edunet took 10.784815549850464s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.5130460262298584s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0006735324859619141s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 13.240202903747559s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7772586345672607s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.18789267539978027s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.559804916381836s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 6.831549644470215s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.17870044708251953s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.24150538444519043s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.14131522178649902s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.16188907623291016s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.14391064643859863s
License | HR license check for Open Research Knowledge Graph (ORKG) took 5.06604266166687s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.18058013916015625s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.18210864067077637s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.33451294898986816s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.13531088829040527s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.17066669464111328s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.16405296325683594s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 11.075492858886719s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.390975952148438e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.17942547798156738s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.16447830200195312s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1561269760131836s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1663508415222168s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.17245078086853027s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3737015724182129s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.3769874572753906s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 6.717111825942993s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.14160537719726562s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.20995092391967773s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.23040437698364258s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 5.3073718547821045s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.2557339668273926s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.26647329330444336s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.19765591621398926s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.6471631526947021s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.9471697807312012s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 5.346155166625977s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.1967921257019043s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.2008891105651855s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2868061065673828s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.15325117111206055s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.14026808738708496s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2092.7386078834534s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 1.504082441329956s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021290302276611328s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 2.0503997802734375e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 7.3909759521484375e-06s
INFO | --- Analysis for orkg took 2378.4531257152557s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.1124517917633057s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.7395009994506836s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.749961853027344e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 8.344650268554688e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 35.135589361190796s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.5649964809417725s
Availability | VoID file availability check for OSM Semantic Network took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.3109138011932373s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.528594970703125e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.152557373046875e-06s
INFO | --- Analysis for osm-semantic-network took 9.823480129241943s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 392.9690434932709s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.696033239364624s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.7670135498046875e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for OTM took 669.6869304180145s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 8.797645568847656e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0003101825714111328s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.26344895362854004s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 8.344650268554688e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 4.734841585159302s
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.0002446174621582031s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.7048830986022949s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02024674415588379s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 3.7552483081817627s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.1484832763671875e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.6994688510894775s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 4.22348690032959s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.291534423828125e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.7043726444244385s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.0994415283203125e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 8.58306884765625e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.345133066177368s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.124641418457031e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.26590800285339355s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 6.9141387939453125e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 3.7651591300964355s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.4345855712890625e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.2678859233856201s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 3.755080223083496s
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.0002503395080566406s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2557699680328369s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 6.9141387939453125e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.96311092376709s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 3.981590270996094e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2653946876525879s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.86102294921875e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 1.2636184692382812e-05s
INFO | --- Analysis for oxpoints took 2.8598220348358154s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.8385624885559082s
Availability | VoID file availability check for Pali English Lexicon took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.2603268623352051s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.9087066650390625e-05s
Believability | Calculation of trust value for Pali English Lexicon took 6.4373016357421875e-06s
INFO | --- Analysis for pali-english-lexicon took 6.977363586425781s
Availability | SPARQL endpoint availability check for PanLex took 0.3987247943878174s
Availability | VoID file availability check for PanLex took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for PanLex took 0.2505984306335449s
Reputation | Calculation of the PageRank for PanLex took 0.020190715789794922s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.224082946777344e-05s
Believability | Calculation of trust value for PanLex took 1.1682510375976562e-05s
INFO | --- Analysis for panlex took 2.7715845108032227s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.220008850097656e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.25278162956237793s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.02025008201599121s
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.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.743171691894531e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 6.4373016357421875e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.941161632537842s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.03531026840209961s
Availability | VoID file availability check for patents.data.gov.uk took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2674739360809326s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02030038833618164s
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.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.6253204345703125e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.392820119857788s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.744529724121094e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0003058910369873047s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.26051759719848633s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02028346061706543s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.600120544433594e-05s
Believability | Calculation of trust value for PDEV-Lemon took 7.152557373046875e-06s
INFO | --- Analysis for pdev-lemon took 3.6649675369262695s
Availability | SPARQL endpoint availability check for pdevlemon took 4.2438507080078125e-05s
Availability | VoID file availability check for pdevlemon took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2673921585083008s
Reputation | Calculation of the PageRank for pdevlemon took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.0994415283203125e-05s
Believability | Calculation of trust value for pdevlemon took 7.62939453125e-06s
INFO | --- Analysis for pdevlemon took 3.0461814403533936s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.1484832763671875e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.000850677490234375s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2638068199157715s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02022099494934082s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.700920104980469e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 6.9141387939453125e-06s
INFO | --- Analysis for periodo took 18.077317237854004s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.3392181396484375e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.25769972801208496s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020264387130737305s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0003886222839355469s
Believability | Calculation of trust value for Personal_Homepages took 7.62939453125e-06s
INFO | --- Analysis for personal-homepages took 2.347608804702759s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology of University People took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.25858497619628906s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.9802322387695312e-05s
Believability | Calculation of trust value for Ontology of University People took 6.4373016357421875e-06s
INFO | --- Analysis for PersonOnto took 2.8155791759490967s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 5.328630685806274s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2648348808288574s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0008242130279541016s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3113021850585938e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.867813110351562e-06s
INFO | --- Analysis for PFKHS took 11.673612356185913s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.5956010818481445s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2749943733215332s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007476806640625s
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 5.7220458984375e-06s
INFO | --- Analysis for PFRPPH took 9.509652376174927s
Availability | SPARQL endpoint availability check for PGxLOD took 0.41233181953430176s
Availability | VoID file availability check for PGxLOD took 0.0006215572357177734s
Extra | Recovery of all triples for PGxLOD took 2.534846782684326s
Performance | Total latancy measurement for PGxLOD took 0.8352012634277344s
Amount of data | Number of triples check for PGxLOD took 0.8013889789581299s
Interoperability | New terms check for PGxLOD took 1.9521913528442383s
Versatility | Languages check for PGxLOD took 60.3614821434021s
Interpretability | Number of blank nodes check for PGxLOD took 1.8391952514648438s
Interpretability | RDF structures check for PGxLOD took 0.40131354331970215s
Versatility | Serialization formats check for PGxLOD took 0.17824935913085938s
Availability | RDF dump link check for PGxLOD took 54.16111874580383s
License | MR license check for PGxLOD took 0.1846601963043213s
License | HR license check for PGxLOD took 60.26389718055725s
Amount of data | Number of property check for PGxLOD took 0.21465420722961426s
Understandability | Number of label check for PGxLOD took 1.2053067684173584s
Understandability | URI regex check for PGxLOD took 0.3647630214691162s
Understandability | Vocabs check for PGxLOD took 0.17550063133239746s
Verifiability | Authors check for PGxLOD took 0.17908167839050293s
Verifiability | Publishers check for PGxLOD took 0.16618919372558594s
Performance | Throughput check for PGxLOD took 10.230308294296265s
Amount of data | Check the number of entities for PGxLOD took 0.11955952644348145s
Verifiability | Contribs. check for PGxLOD took 0.16442656517028809s
Interlinking | sameAs chians check for PGxLOD took 0.28670263290405273s
Interlinking | skos check for PGxLOD took 0.26384878158569336s
Interlinking | skos check for PGxLOD took 0.20530438423156738s
Timeliness | dataset update frequency check for PGxLOD took 0.1734144687652588s
Currency | Creation date check for PGxLOD took 0.34897685050964355s
Currency | Modification date check for PGxLOD took 0.3499264717102051s
Rep.Conc. | URIs length for PGxLOD took 6.825819492340088s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.1714181900024414s
Accuracy | Check Functional Property for PGxLOD took 0.21079111099243164s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.2101593017578125s
Accuracy | Check Empty annotation labels for PGxLOD took 1.1150078773498535s
Accuracy | Check White space in annotation for PGxLOD took 0.03688764572143555s
Accuracy | Check Datatype consistency for PGxLOD took 0.030674457550048828s
Consistency | Disjoint class check for PGxLOD took 0.16727495193481445s
Consistency | Check Misplaced properties for PGxLOD took 6.922896146774292s
Consistency | Misplaced classes for PGxLOD took 0.3074002265930176s
Consistency | Check Ontology hijacking for PGxLOD took 2.001234531402588s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.185196876525879s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.558631181716919s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03162574768066406s
Conciseness | Check Intensional conciseness for PGxLOD took 0.267254114151001s
Security | Sign check for PGxLOD took 0.18317270278930664s
Availability | Check URIs Dereferenciability for PGxLOD took 1691.6620695590973s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.9069244861602783s
Reputation | Calculation of the PageRank for PGxLOD took 0.023124217987060547s
Interlinking | Calculation of Degree of Connection for PGxLOD took 3.170967102050781e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0009064674377441406s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 7.843971252441406e-05s
Believability | Calculation of trust value for PGxLOD took 9.059906005859375e-06s
INFO | --- Analysis for PGxLOD took 3029.8466460704803s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.3057796955108643s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007984638214111328s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.6988811492919922s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 4.506111145019531e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 8.821487426757812e-06s
INFO | --- Analysis for phoible took 7.355600833892822s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.315376281738281e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.25830626487731934s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.9802322387695312e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 7.3909759521484375e-06s
INFO | --- Analysis for PISM took 16.747368574142456s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.2438507080078125e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.26221776008605957s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.463859558105469e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.049041748046875e-05s
INFO | --- Analysis for planetdata-project-wiki took 3.781334400177002s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.0027458667755127s
Availability | VoID file availability check for digitized plant specimen took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.2550816535949707s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.02112126350402832s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.462501525878906e-05s
Believability | Calculation of trust value for digitized plant specimen took 9.059906005859375e-06s
INFO | --- Analysis for plant-specimen took 3.3728904724121094s
Availability | SPARQL endpoint availability check for Pleiades took 4.5299530029296875e-05s
Availability | VoID file availability check for Pleiades took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Pleiades took 0.6993215084075928s
Reputation | Calculation of the PageRank for Pleiades took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Pleiades took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Pleiades took 7.843971252441406e-05s
Believability | Calculation of trust value for Pleiades took 7.62939453125e-06s
INFO | --- Analysis for pleiades took 16.38891363143921s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.1961669921875e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.7029242515563965s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020762920379638672s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0008959770202636719s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.62396240234375e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.867813110351562e-06s
INFO | --- Analysis for podorozhnyk took 4.946884870529175s
Availability | SPARQL endpoint availability check for Poképédia took 4.38690185546875e-05s
Availability | VoID file availability check for Poképédia took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2520406246185303s
Reputation | Calculation of the PageRank for Poképédia took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for Poképédia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Poképédia took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Poképédia took 6.961822509765625e-05s
Believability | Calculation of trust value for Poképédia took 7.152557373046875e-06s
INFO | --- Analysis for pokepedia-fr took 2.916952133178711s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.410743713378906e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.2622661590576172s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.367134094238281e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 5.9604644775390625e-06s
INFO | --- Analysis for polymath-virtual-library took 6.209314823150635s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.89241623878479s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0003337860107421875s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2653920650482178s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2159347534179688e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.67572021484375e-06s
INFO | --- Analysis for portuguese_prisons_releases took 6.695668458938599s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.172325134277344e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.2553572654724121s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020185470581054688s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.0279159545898438e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 6.67572021484375e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.859793186187744s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.1484832763671875e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.25285959243774414s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.9087066650390625e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 7.152557373046875e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.7792155742645264s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.1484832763671875e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.26076269149780273s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 6.079673767089844e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 7.62939453125e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 3.2807226181030273s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 5.14984130859375e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2497868537902832s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007483959197998047s
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 7.62939453125e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.812340021133423s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 5.030632019042969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.25420665740966797s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.7948572635650635s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.24887847900390625s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020339488983154297s
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.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.820600748062134s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2597615718841553s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.0205838680267334s
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.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.8375368118286133s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.25575971603393555s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.8022356033325195s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.2590961456298828s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.8400838375091553s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2680988311767578s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.815645456314087s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 8.368492126464844e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2614262104034424s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.02310466766357422s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0011789798736572266s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.8623809814453125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.815086841583252s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.315376281738281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.25742483139038086s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 9.059906005859375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.854520082473755s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2541215419769287s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 3.838539123535156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.8578169345855713s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.26343345642089844s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.8740930557250977s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2544739246368408s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.8883280754089355s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.26598525047302246s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.9154415130615234s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 5.1975250244140625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.25266265869140625s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.7911341190338135s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2599339485168457s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 1.2636184692382812e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.860428810119629s
Availability | SPARQL endpoint availability check for prefix.cc took 4.410743713378906e-05s
Availability | VoID file availability check for prefix.cc took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2587471008300781s
Reputation | Calculation of the PageRank for prefix.cc took 0.020159482955932617s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.814697265625e-05s
Believability | Calculation of trust value for prefix.cc took 6.198883056640625e-06s
INFO | --- Analysis for prefix-cc took 3.176372766494751s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 2.1470863819122314s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2647256851196289s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.649162292480469e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 6.67572021484375e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 9.457317352294922s
