Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 5.650520324707031e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.29003143310546875s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.45186328887939453s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0006306171417236328s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.1205673217773438e-05s
INFO | --- Analysis for 0080-3626 took 5.86274528503418s
Availability | SPARQL endpoint availability check for 土地利用图 took 0.0001010894775390625s
Availability | VoID file availability check for 土地利用图 took 0.000518798828125s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.2986886501312256s
Reputation | Calculation of the PageRank for 土地利用图 took 0.021778583526611328s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 5.435943603515625e-05s
Believability | Calculation of trust value for 土地利用图 took 1.5497207641601562e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.791334390640259s
Availability | SPARQL endpoint availability check for 113322 took 0.00018715858459472656s
Availability | VoID file availability check for 113322 took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for 113322 took 0.2810225486755371s
Reputation | Calculation of the PageRank for 113322 took 0.020268678665161133s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 113322 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.361701965332031e-05s
Believability | Calculation of trust value for 113322 took 1.33514404296875e-05s
INFO | --- Analysis for 11 took 4.457314491271973s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 7.987022399902344e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.30745935440063477s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.147125244140625e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.3113021850585938e-05s
INFO | --- Analysis for 12323 took 2.7088232040405273s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.07867050170898438s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.3068053722381592s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.059906005859375e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.0013580322265625e-05s
INFO | --- Analysis for 2000-us-census-rdf took 2.7078166007995605s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.8449842929840088s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2767179012298584s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 5.173683166503906e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 7.867813110351562e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.35008692741394s
Availability | SPARQL endpoint availability check for Open Data Web took 185.479327917099s
Availability | VoID file availability check for Open Data Web took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.31402158737182617s
Reputation | Calculation of the PageRank for Open Data Web took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.887580871582031e-05s
Believability | Calculation of trust value for Open Data Web took 1.2159347534179688e-05s
INFO | --- Analysis for _data.odw.tw took 252.67466187477112s
Availability | SPARQL endpoint availability check for 土地利用 took 9.393692016601562e-05s
Availability | VoID file availability check for 土地利用 took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.30447983741760254s
Reputation | Calculation of the PageRank for 土地利用 took 0.020313501358032227s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.956390380859375e-05s
Believability | Calculation of trust value for 土地利用 took 1.0013580322265625e-05s
INFO | --- Analysis for _data1.odw.tw took 2.7661056518554688s
Availability | SPARQL endpoint availability check for 土地利用模型 took 9.393692016601562e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2946772575378418s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.86102294921875e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.049041748046875e-05s
INFO | --- Analysis for _data2.odw.tw took 4.257665634155273s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.083747863769531e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.31542277336120605s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021073102951049805s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.123283386230469e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 4.026605844497681s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 0.00010275840759277344s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2996485233306885s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.170967102050781e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.0728836059570312e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.464904308319092s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.410743713378906e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.33043622970581055s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.0517578125e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 7.867813110351562e-06s
INFO | --- Analysis for A1 took 3.771064519882202s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.8428046703338623s
Availability | VoID file availability check for SummerOlympics took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.38218069076538086s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.4849853515625e-05s
Believability | Calculation of trust value for SummerOlympics took 1.0251998901367188e-05s
INFO | --- Analysis for abc took 9.310299634933472s
Availability | SPARQL endpoint availability check for Test_m took 9.703636169433594e-05s
Availability | VoID file availability check for Test_m took 0.001188039779663086s
Completeness | Calculation of interlinking completeness for Test_m took 0.31552791595458984s
Reputation | Calculation of the PageRank for Test_m took 0.0220181941986084s
Interlinking | Calculation of Degree of Connection for Test_m took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.123283386230469e-05s
Believability | Calculation of trust value for Test_m took 1.3589859008789062e-05s
INFO | --- Analysis for ABC took 2.6290550231933594s
Availability | SPARQL endpoint availability check for my intro took 4.792213439941406e-05s
Availability | VoID file availability check for my intro took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for my intro took 0.2770206928253174s
Reputation | Calculation of the PageRank for my intro took 0.021201610565185547s
Interlinking | Calculation of Degree of Connection for my intro took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for my intro took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for my intro took 3.0517578125e-05s
Believability | Calculation of trust value for my intro took 1.2636184692382812e-05s
INFO | --- Analysis for abhay_intro took 2.6199703216552734s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.1053304672241211s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.29801464080810547s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.021945953369140625s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010323524475097656s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for abs-linked-data took 2.851353645324707s
Availability | SPARQL endpoint availability check for AcadOnto took 9.465217590332031e-05s
Availability | VoID file availability check for AcadOnto took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.27494192123413086s
Reputation | Calculation of the PageRank for AcadOnto took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.266334533691406e-05s
Believability | Calculation of trust value for AcadOnto took 1.3589859008789062e-05s
INFO | --- Analysis for acadonto took 3.128431797027588s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 11.454373836517334s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.29662561416625977s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.021558046340942383s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.8623809814453125e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for acorn-sat took 38.4647421836853s
Availability | SPARQL endpoint availability check for Addgene took 9.298324584960938e-05s
Availability | VoID file availability check for Addgene took 0.0007963180541992188s
Completeness | Calculation of interlinking completeness for Addgene took 0.2965371608734131s
Reputation | Calculation of the PageRank for Addgene took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for Addgene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.647804260253906e-05s
Believability | Calculation of trust value for Addgene took 1.1920928955078125e-05s
INFO | --- Analysis for addgene took 16.075216054916382s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 9.417533874511719e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2881436347961426s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.021166086196899414s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0009305477142333984s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 0.00011539459228515625s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.1920928955078125e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 11.111485242843628s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.4701836109161377s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.2833867073059082s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.021096467971801758s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.6716461181640625e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.1920928955078125e-05s
INFO | --- Analysis for aemet took 4.907964468002319s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03493165969848633s
Availability | VoID file availability check for AgriNepalData took 0.0011954307556152344s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2918672561645508s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.05718994140625e-05s
Believability | Calculation of trust value for AgriNepalData took 1.2636184692382812e-05s
INFO | --- Analysis for agrinepaldata took 2.7923007011413574s
Availability | SPARQL endpoint availability check for AGRIS took 260.7880690097809s
Availability | VoID file availability check for AGRIS took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for AGRIS took 0.315004825592041s
Reputation | Calculation of the PageRank for AGRIS took 0.020814895629882812s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.891654968261719e-05s
Believability | Calculation of trust value for AGRIS took 1.2636184692382812e-05s
INFO | --- Analysis for agris took 572.5225999355316s
Availability | SPARQL endpoint availability check for AGROVOC took 0.18397021293640137s
Availability | VoID file availability check for AGROVOC took 0.0006260871887207031s
Extra | Recovery of all triples for AGROVOC took 29.974451303482056s
Performance | Total latancy measurement for AGROVOC took 0.47203493118286133s
Amount of data | Number of triples check for AGROVOC took 15.146915912628174s
Interoperability | New terms check for AGROVOC took 3.056772232055664s
Versatility | Languages check for AGROVOC took 47.295363426208496s
Interpretability | Number of blank nodes check for AGROVOC took 12.874196529388428s
Interpretability | RDF structures check for AGROVOC took 0.0781104564666748s
Versatility | Serialization formats check for AGROVOC took 0.09696078300476074s
Availability | RDF dump link check for AGROVOC took 0.09890413284301758s
License | MR license check for AGROVOC took 0.0983428955078125s
License | HR license check for AGROVOC took 0.414867639541626s
Amount of data | Number of property check for AGROVOC took 0.08936905860900879s
Understandability | Number of label check for AGROVOC took 22.227582931518555s
Understandability | URI regex check for AGROVOC took 0.22365045547485352s
Understandability | Vocabs check for AGROVOC took 0.08629107475280762s
Verifiability | Authors check for AGROVOC took 0.09941458702087402s
Verifiability | Publishers check for AGROVOC took 0.0985100269317627s
Performance | Throughput check for AGROVOC took 10.580445766448975s
Amount of data | Check the number of entities for AGROVOC took 7.772445678710938e-05s
Verifiability | Contribs. check for AGROVOC took 0.0773012638092041s
Interlinking | sameAs chians check for AGROVOC took 0.0864715576171875s
Interlinking | skos check for AGROVOC took 0.45467257499694824s
Interlinking | skos check for AGROVOC took 0.41538286209106445s
Timeliness | dataset update frequency check for AGROVOC took 0.09942483901977539s
Currency | Creation date check for AGROVOC took 0.23643708229064941s
Currency | Modification date check for AGROVOC took 0.178178071975708s
Rep.Conc. | URIs length for AGROVOC took 41.86023664474487s
Interoperability | New vocabularies check for AGROVOC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.07401466369628906s
Accuracy | Check Functional Property for AGROVOC took 0.08275961875915527s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.09392046928405762s
Accuracy | Check Empty annotation labels for AGROVOC took 16.178351640701294s
Accuracy | Check White space in annotation for AGROVOC took 2.9742507934570312s
Accuracy | Check Datatype consistency for AGROVOC took 4.432115316390991s
Consistency | Disjoint class check for AGROVOC took 0.08414506912231445s
Consistency | Check Misplaced properties for AGROVOC took 11.823159217834473s
Consistency | Check Ontology hijacking for AGROVOC took 21.18705916404724s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.5661125183105469s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 14.186008214950562s
Conciseness | Check Extensional conciseness for AGROVOC took 2.6395018100738525s
Conciseness | Check Intensional conciseness for AGROVOC took 0.08638834953308105s
Security | Sign check for AGROVOC took 0.0818026065826416s
Availability | Check URIs Dereferenciability for AGROVOC took 2362.3023643493652s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.6958808898925781s
Reputation | Calculation of the PageRank for AGROVOC took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00017690658569335938s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 1.049041748046875e-05s
INFO | --- Analysis for agrovoc took 2668.439106941223s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.1552152633666992s
Availability | VoID file availability check for Analytics India Magazine took 0.0006384849548339844s
Extra | Recovery of all triples for Analytics India Magazine took 2.2835068702697754s
Performance | Total latancy measurement for Analytics India Magazine took 1.2954189777374268s
Amount of data | Number of triples check for Analytics India Magazine took 1.2675719261169434s
Versatility | Languages check for Analytics India Magazine took 1.6413636207580566s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.1582458019256592s
Interpretability | RDF structures check for Analytics India Magazine took 1.7512667179107666s
Versatility | Serialization formats check for Analytics India Magazine took 1.129606008529663s
Availability | RDF dump link check for Analytics India Magazine took 1.773367166519165s
License | MR license check for Analytics India Magazine took 1.5935943126678467s
License | HR license check for Analytics India Magazine took 1.374774694442749s
Amount of data | Number of property check for Analytics India Magazine took 1.3339884281158447s
Understandability | Number of label check for Analytics India Magazine took 1.4661064147949219s
Understandability | URI regex check for Analytics India Magazine took 2.479539155960083s
Understandability | Vocabs check for Analytics India Magazine took 1.7943205833435059s
Verifiability | Authors check for Analytics India Magazine took 1.255347728729248s
Verifiability | Publishers check for Analytics India Magazine took 1.0718719959259033s
Performance | Throughput check for Analytics India Magazine took 15.800062417984009s
Amount of data | Check the number of entities for Analytics India Magazine took 4.6253204345703125e-05s
Verifiability | Contribs. check for Analytics India Magazine took 1.4080240726470947s
Interlinking | sameAs chians check for Analytics India Magazine took 1.1682517528533936s
Interlinking | skos check for Analytics India Magazine took 1.6655733585357666s
Interlinking | skos check for Analytics India Magazine took 0.1372661590576172s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.3868131637573242s
Currency | Creation date check for Analytics India Magazine took 2.780758857727051s
Currency | Modification date check for Analytics India Magazine took 2.6393957138061523s
Rep.Conc. | URIs length for Analytics India Magazine took 3.7182724475860596s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.3925197124481201s
Consistency | Disjoint class check for Analytics India Magazine took 1.117732048034668s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.417902946472168s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.974436044692993s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00015211105346679688s
Security | Sign check for Analytics India Magazine took 1.4769203662872314s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.29050540924072266s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.86102294921875e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 9.5367431640625e-07s
Believability | Calculation of trust value for Analytics India Magazine took 9.5367431640625e-06s
INFO | --- Analysis for AIM took 101.19992184638977s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 9.250640869140625e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0003840923309326172s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.29263997077941895s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020493745803833008s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.123283386230469e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 5.4836273193359375e-06s
INFO | --- Analysis for AISHE took 2.702733039855957s
Availability | SPARQL endpoint availability check for  equipment ontology took 0.00021195411682128906s
Availability | VoID file availability check for  equipment ontology took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.29549598693847656s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for  equipment ontology took 1.2874603271484375e-05s
INFO | --- Analysis for akash took 2.671710729598999s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 261.6232531070709s
Availability | VoID file availability check for aliada-scanbit-net took 0.0008800029754638672s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.4026165008544922s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00012183189392089844s
Believability | Calculation of trust value for aliada-scanbit-net took 1.2159347534179688e-05s
INFO | --- Analysis for aliada-scanbit-net took 1450.9538187980652s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.6219353675842285s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0005691051483154297s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 136.57538485527039s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.725957155227661s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.368605613708496s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.573566436767578s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0192406177521s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 4.058208703994751s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 2.4762940406799316s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.8820540904998779s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 1.024569034576416s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5600242614746094s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5778687000274658s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 34.136351585388184s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5741221904754639s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 3.382225513458252s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.096717119216919s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5622572898864746s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6821181774139404s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.739619255065918s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 11.703444719314575s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 7.653236389160156e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5762662887573242s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.578157901763916s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5671370029449463s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5493440628051758s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5691952705383301s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.8606760501861572s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1112432479858398s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 51.264902114868164s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.5594375133514404s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5714259147644043s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.673591136932373s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.7082498073577881s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 33.87461757659912s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0570454597473145s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.5896308422088623s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6117782592773438s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.474973917007446s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.695587396621704s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 33.883716344833374s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.4846532344818115s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.349499464035034s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.81624436378479s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8347198963165283s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5791857242584229s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 14219.354341983795s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.46883606910705566s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02357649803161621s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.00018668174743652344s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.2187347412109375s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.71661376953125e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14977.192300319672s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.2817654609680176s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.3173365592956543s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.022159099578857422s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.100799560546875e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.4781951904296875e-05s
INFO | --- Analysis for alpino-rdf took 3.8872320652008057s
Availability | SPARQL endpoint availability check for AAT-atawil took 0.00011849403381347656s
Availability | VoID file availability check for AAT-atawil took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2995421886444092s
Reputation | Calculation of the PageRank for AAT-atawil took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.123283386230469e-05s
Believability | Calculation of trust value for AAT-atawil took 9.5367431640625e-06s
INFO | --- Analysis for Altawil took 2.645402669906616s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.363059997558594e-05s
Availability | VoID file availability check for Amer Nejma took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.27983951568603516s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020804405212402344s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.147125244140625e-05s
Believability | Calculation of trust value for Amer Nejma took 1.33514404296875e-05s
INFO | --- Analysis for Amer_Nejma took 2.6444473266601562s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7565560340881348s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2991199493408203s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.022374629974365234s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.846687316894531e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0251998901367188e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 4.561480283737183s
Availability | SPARQL endpoint availability check for Anime Dataset took 5.888938903808594e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.30379152297973633s
Reputation | Calculation of the PageRank for Anime Dataset took 0.022179841995239258s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.3855438232421875e-05s
Believability | Calculation of trust value for Anime Dataset took 1.049041748046875e-05s
INFO | --- Analysis for Anime took 3.8573739528656006s
Availability | SPARQL endpoint availability check for ANNO took 9.489059448242188e-05s
Availability | VoID file availability check for ANNO took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for ANNO took 0.313784122467041s
Reputation | Calculation of the PageRank for ANNO took 0.021826744079589844s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for ANNO took 4.315376281738281e-05s
Believability | Calculation of trust value for ANNO took 1.1682510375976562e-05s
INFO | --- Analysis for anno took 8.741070985794067s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 9.226799011230469e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2965269088745117s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.02112722396850586s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 8.440017700195312e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.239776611328125e-05s
INFO | --- Analysis for AntiqueCarsCollection took 3.283365249633789s
Availability | SPARQL endpoint availability check for apache took 4.57763671875e-05s
Availability | VoID file availability check for apache took 0.00147247314453125s
Completeness | Calculation of interlinking completeness for apache took 0.28907060623168945s
Reputation | Calculation of the PageRank for apache took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for apache took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for apache took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for apache took 5.8650970458984375e-05s
Believability | Calculation of trust value for apache took 1.4543533325195312e-05s
INFO | --- Analysis for apache took 3.5656514167785645s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.30476951599121094s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf took 6.20055365562439s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 9.799003601074219e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.3290109634399414s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 6.088365793228149s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 8.96453857421875e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.28954529762268066s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.021096229553222656s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 5.851730108261108s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 9.489059448242188e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.28250837326049805s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02126789093017578s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.863739013671875e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-en-es took 5.977426767349243s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 9.5367431640625e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0013229846954345703s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.29584431648254395s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020731449127197266s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 5.936436653137207s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 9.298324584960938e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.27777671813964844s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 5.1021575927734375e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 8.821487426757812e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.784184217453003s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 8.988380432128906e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2867093086242676s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02101922035217285s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 5.895716667175293s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2759995460510254s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.021066665649414062s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0008406639099121094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.888938903808594e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 5.779135465621948s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.8160552978515625e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.29695725440979004s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.021236419677734375s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0010099411010742188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 5.5789947509765625e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.847765922546387s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 0.00013494491577148438s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.30198144912719727s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.0219724178314209s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-es-an took 6.022631883621216s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 8.916854858398438e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.29744958877563477s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020803213119506836s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 6.41768741607666s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 8.845329284667969e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.319516658782959s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.021062374114990234s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 25.381826877593994s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 8.940696716308594e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.28900790214538574s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.022606849670410156s
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.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.316734313964844e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 5.814515113830566s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 9.393692016601562e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.4117403030395508s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.76837158203125e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 5.880451440811157s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.792213439941406e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2859628200531006s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02148604393005371s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.951807260513306s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 8.678436279296875e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.33629727363586426s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 5.911980867385864s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 9.083747863769531e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.27544140815734863s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02241230010986328s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 5.883051156997681s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 9.679794311523438e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0007786750793457031s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2857627868652344s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.900599956512451s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.26610612869262695s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.021100759506225586s
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.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.913506746292114s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 0.000118255615234375s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.3033103942871094s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.813809871673584s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 9.250640869140625e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.29871463775634766s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 5.905629396438599s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 9.036064147949219e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2795538902282715s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.986034154891968s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 9.274482727050781e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.33483266830444336s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02094864845275879s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.657970905303955s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.6682446002960205s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0006234645843505859s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 4.117990016937256s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.956202745437622s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.7794022560119629s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.1875932216644287s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.490686655044556s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 3.9393150806427s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.2799046039581299s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.8030014038085938s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.96651291847229s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.3992922306060791s
License | MR license check for AragoDBpedia - aragon open data took 0.8097391128540039s
License | HR license check for AragoDBpedia - aragon open data took 6.970099687576294s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.43632960319519043s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.5906555652618408s
Understandability | URI regex check for AragoDBpedia - aragon open data took 1.022960901260376s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.47245240211486816s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.5419981479644775s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.41277480125427246s
Performance | Throughput check for AragoDBpedia - aragon open data took 11.408090114593506s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 7.104873657226562e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.5788600444793701s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.47332334518432617s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.6983737945556641s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.39617133140563965s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.5159657001495361s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.2658138275146484s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.4098668098449707s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 6.021528720855713s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.37601804733276367s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.5090980529785156s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.46144604682922363s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.4687657356262207s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.030637264251708984s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.02763652801513672s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.4291813373565674s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.3472676277160645s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.6110374927520752s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.514777898788452s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.338022232055664s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.240778923034668s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.032825469970703125s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.6648097038269043s
Security | Sign check for AragoDBpedia - aragon open data took 0.5840036869049072s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 3264.945474386215s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.7756364345550537s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.021294832229614258s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBpedia - aragon open data took 1.9073486328125e-06s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 9.059906005859375e-06s
INFO | --- Analysis for aragodbpedia took 3548.690231323242s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.292482376098633s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.32801103591918945s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 6.866455078125e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 3.075599670410156e-05s
INFO | --- Analysis for archiveshub-linkeddata took 83.39494466781616s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.070397853851318s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.3139958381652832s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 2.956390380859375e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.1205673217773438e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 21.32856035232544s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.91273832321167s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0014410018920898438s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.30423688888549805s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02208423614501953s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.0531158447265625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.3113021850585938e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 17.181478023529053s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.107589721679688e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0008189678192138672s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.29503488540649414s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.021168231964111328s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0009918212890625s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0001499652862548828s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.2874603271484375e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 55.22946763038635s
Availability | SPARQL endpoint availability check for Arthroscopy community took 9.012222290039062e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.29623889923095703s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02097773551940918s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010776519775390625s
Believability | Calculation of trust value for Arthroscopy community took 1.2636184692382812e-05s
INFO | --- Analysis for arthroscopy took 29.26114535331726s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 1.749662160873413s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0007197856903076172s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 41.26022672653198s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.2327322959899902s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.17327737808228s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.024829864501953s
Versatility | Languages check for Wikidata entry for Art × Science International took 65.1660373210907s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.170569896698s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.5147197246551514s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.20709586143493652s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.15864348411560059s
License | MR license check for Wikidata entry for Art × Science International took 0.4022819995880127s
License | HR license check for Wikidata entry for Art × Science International took 65.15666627883911s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.6663198471069336s
Understandability | Number of label check for Wikidata entry for Art × Science International took 60.17695331573486s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.3671538829803467s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.2989182472229004s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.26341938972473145s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.31043481826782227s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 8.559226989746094e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.1878666877746582s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 65.17269158363342s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.39311933517456055s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.08419203758239746s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.18610548973083496s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.39856863021850586s
Currency | Modification date check for Wikidata entry for Art × Science International took 1.072798252105713s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 40.6564884185791s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.1844005584716797s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 19.367834329605103s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.675537586212158s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.507875680923462s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.1931746006011963s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 16.793826818466187s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 9.786239862442017s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 39.49639844894409s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.4221653938293457s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 2.337482452392578s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.894745111465454s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.7202439308166504s
Security | Sign check for Wikidata entry for Art × Science International took 0.17990994453430176s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 8.768979787826538s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.40526676177978516s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020952224731445312s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.4066696166992188e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 2.6226043701171875e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.3828277587890625e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 966.8256824016571s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.176037311553955s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.29900622367858887s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.843971252441406e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.5367431640625e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 12.134514331817627s
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.166611909866333s
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.00058746337890625s
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.2805135250091553s
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.021795988082885742s
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.049041748046875e-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.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.891654968261719e-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 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 10.495938539505005s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.1804418563842773s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2747061252593994s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.107589721679688e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 11.51077389717102s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.1548361778259277s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.3101165294647217s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.023374557495117188s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.458427429199219e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-CRB took 13.486597299575806s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.1520538330078125s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.29805850982666016s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.012222290039062e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0728836059570312e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.238736152648926s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.163569688796997s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2885723114013672s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.021232128143310547s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-DQOT took 12.001062631607056s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.17348313331604s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.29027485847473145s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.022057056427001953s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.130073547363281e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.046349048614502s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.894240379333496s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.2867748737335205s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.0228121280670166s
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.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.296966552734375e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 14.200154781341553s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.165199041366577s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.30330395698547363s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.021486997604370117s
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.0013580322265625e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.364418029785156e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.123347282409668s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.16819429397583s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.30403614044189453s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.021224260330200195s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.984306335449219e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.049041748046875e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.16352128982544s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.451479911804199s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2748682498931885s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.022626399993896484s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.33514404296875e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 15.045191287994385s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.1736249923706055s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2765960693359375s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.021056652069091797s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.724761962890625e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 10.591227531433105s
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.1652026176452637s
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.0007424354553222656s
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.29386425018310547s
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.020588159561157227s
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.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.177757263183594e-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 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.062133550643921s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.175661563873291s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.3261294364929199s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.38690185546875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC_-_DNB took 10.667428255081177s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 9.274482727050781e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2911231517791748s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.771087646484375e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.2874603271484375e-05s
INFO | --- Analysis for asit took 7.806746959686279s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 0.00010967254638671875s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.298403263092041s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.022206544876098633s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.0531158447265625e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.049041748046875e-05s
INFO | --- Analysis for asjp took 4.982274770736694s
Availability | SPARQL endpoint availability check for ASN:US took 2.2932870388031006s
Availability | VoID file availability check for ASN:US took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for ASN:US took 0.30465078353881836s
Reputation | Calculation of the PageRank for ASN:US took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.437301635742188e-05s
Believability | Calculation of trust value for ASN:US took 8.106231689453125e-06s
INFO | --- Analysis for asn-us took 13.051340341567993s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.2438507080078125e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.28244662284851074s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.8133392333984375e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 3.814697265625e-06s
INFO | --- Analysis for aspire-mmu took 4.792745113372803s
Availability | SPARQL endpoint availability check for associations took 0.00010633468627929688s
Availability | VoID file availability check for associations took 0.0009603500366210938s
Completeness | Calculation of interlinking completeness for associations took 0.32924652099609375s
Reputation | Calculation of the PageRank for associations took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for associations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for associations took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for associations took 7.82012939453125e-05s
Believability | Calculation of trust value for associations took 1.3828277587890625e-05s
INFO | --- Analysis for associations took 8.275867700576782s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.9591064453125e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.28894567489624023s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.940696716308594e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.2874603271484375e-05s
INFO | --- Analysis for athelia-rfid took 49.94613480567932s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.6829202175140381s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.28797411918640137s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02193617820739746s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.221366882324219e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.427446365356445s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.4867575168609619s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.29061412811279297s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.584426879882812e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.3113021850585938e-05s
INFO | --- Analysis for austrian_ski_racers took 3.9246084690093994s
Availability | SPARQL endpoint availability check for AVsOnto took 9.369850158691406e-05s
Availability | VoID file availability check for AVsOnto took 0.00067138671875s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.30541372299194336s
Reputation | Calculation of the PageRank for AVsOnto took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for AVsOnto took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 2.9087066650390625e-05s
Believability | Calculation of trust value for AVsOnto took 1.2159347534179688e-05s
INFO | --- Analysis for AVsOnto took 3.472463369369507s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3915221691131592s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0006780624389648438s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 204.3144030570984s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5022518634796143s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0939221382141s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 201.43322157859802s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.08031392097473s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.07987809181213s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2105998992919922s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.31450390815734863s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2391972541809082s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09905171394348145s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 54.67280840873718s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0836374759674s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1344451904296875s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 207.53419589996338s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3283355236053467s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12372970581054688s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12329530715942383s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14312410354614258s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.565546751022339s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.295608520507812e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1241750717163086s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0954439640045s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17458200454711914s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16269493103027344s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14797544479370117s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2155613899230957s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3529927730560303s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 832.2360374927521s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1643543243408203s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.538089752197266s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.229980707168579s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.754122018814087s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1392199993133545s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.21246576309204s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 457.64174818992615s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.43975567817688s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.52426767349243s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.942117929458618s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21359944343566895s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0830192565917969s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.8345222473144531s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021276473999023438s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.152557373046875e-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 7.867813110351562e-06s
INFO | --- Analysis for b3kat took 4743.506153583527s
Availability | SPARQL endpoint availability check for BabelNet took 0.4234294891357422s
Availability | VoID file availability check for BabelNet took 0.000308990478515625s
Completeness | Calculation of interlinking completeness for BabelNet took 0.307220458984375s
Reputation | Calculation of the PageRank for BabelNet took 0.021051883697509766s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001647472381591797s
Believability | Calculation of trust value for BabelNet took 6.9141387939453125e-06s
INFO | --- Analysis for babelnet took 4.443675518035889s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 8.845329284667969e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.3031425476074219s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.3589859008789062e-05s
INFO | --- Analysis for Bacevicius.lt took 2.5889930725097656s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.42954397201538086s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2781498432159424s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020939111709594727s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.649162292480469e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.049041748046875e-05s
INFO | --- Analysis for bag took 4.300607204437256s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 1.4193804264068604s
Availability | VoID file availability check for 红色经典歌曲 took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2758152484893799s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02128744125366211s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0994415283203125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.0251998901367188e-05s
INFO | --- Analysis for baixue took 4.153346061706543s
Availability | SPARQL endpoint availability check for baixue composer took 9.107589721679688e-05s
Availability | VoID file availability check for baixue composer took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for baixue composer took 0.32417893409729004s
Reputation | Calculation of the PageRank for baixue composer took 0.02210092544555664s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.147125244140625e-05s
Believability | Calculation of trust value for baixue composer took 9.5367431640625e-06s
INFO | --- Analysis for baixue_composer took 3.2641851902008057s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.489059448242188e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.32813072204589844s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02167034149169922s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0008292198181152344s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.504753112792969e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1920928955078125e-05s
INFO | --- Analysis for baixue_imagery took 3.014113664627075s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.887580871582031e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.28015851974487305s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.266334533691406e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1920928955078125e-05s
INFO | --- Analysis for baixue_imagery1 took 4.301906108856201s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.482269287109375e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.27573299407958984s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02110886573791504s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.267692565917969e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.0967254638671875e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.2590267658233643s
Availability | SPARQL endpoint availability check for BBC Music took 0.607614278793335s
Availability | VoID file availability check for BBC Music took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for BBC Music took 0.28684139251708984s
Reputation | Calculation of the PageRank for BBC Music took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0008633136749267578s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001430511474609375s
Believability | Calculation of trust value for BBC Music took 1.239776611328125e-05s
INFO | --- Analysis for bbc-music took 3.9370956420898438s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.28224968910217285s
Availability | VoID file availability check for BBC Programmes took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2783203125s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020846128463745117s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010514259338378906s
Believability | Calculation of trust value for BBC Programmes took 1.2874603271484375e-05s
INFO | --- Analysis for bbc-programmes took 11.151495695114136s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.25788044929504395s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0008075237274169922s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.33492064476013184s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.021251201629638672s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010371208190917969s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.1205673217773438e-05s
INFO | --- Analysis for bbc-wildlife-finder took 9.966793298721313s
Availability | SPARQL endpoint availability check for BBOP took 4.482269287109375e-05s
Availability | VoID file availability check for BBOP took 0.0010235309600830078s
Completeness | Calculation of interlinking completeness for BBOP took 0.29552388191223145s
Reputation | Calculation of the PageRank for BBOP took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.218650817871094e-05s
Believability | Calculation of trust value for BBOP took 1.049041748046875e-05s
INFO | --- Analysis for bbop-selected took 21.185399293899536s
Availability | SPARQL endpoint availability check for Bdgp took 1.1352179050445557s
Availability | VoID file availability check for Bdgp took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Bdgp took 0.29489946365356445s
Reputation | Calculation of the PageRank for Bdgp took 0.021041154861450195s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.361701965332031e-05s
Believability | Calculation of trust value for Bdgp took 1.1444091796875e-05s
INFO | --- Analysis for bdgp took 5.328705072402954s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.410743713378906e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.2772989273071289s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.218650817871094e-05s
Believability | Calculation of trust value for Bendev Junior took 5.9604644775390625e-06s
INFO | --- Analysis for bendevoficial took 3.24554443359375s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 7.385426998138428s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0003180503845214844s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.3000507354736328s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020758867263793945s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.771087646484375e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 8.344650268554688e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 21.117750883102417s
Availability | SPARQL endpoint availability check for berlios took 4.315376281738281e-05s
Availability | VoID file availability check for berlios took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for berlios took 0.2875361442565918s
Reputation | Calculation of the PageRank for berlios took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for berlios took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for berlios took 9.012222290039062e-05s
Believability | Calculation of trust value for berlios took 9.775161743164062e-06s
INFO | --- Analysis for berlios took 3.0972912311553955s
Availability | SPARQL endpoint availability check for Between Our Worlds took 9.72747802734375e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.35451507568359375s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02120518684387207s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.62939453125e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.049041748046875e-05s
INFO | --- Analysis for betweenourworlds took 9.2339448928833s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.10226011276245117s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.29762697219848633s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02092266082763672s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.34600830078125e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for bfs-linked-data took 2.92536997795105s
Availability | SPARQL endpoint availability check for BibBase took 0.0818777084350586s
Availability | VoID file availability check for BibBase took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for BibBase took 0.32178544998168945s
Reputation | Calculation of the PageRank for BibBase took 0.02180194854736328s
Interlinking | Calculation of Degree of Connection for BibBase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.799003601074219e-05s
Believability | Calculation of trust value for BibBase took 1.0013580322265625e-05s
INFO | --- Analysis for bibbase took 2.8391592502593994s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.869171142578125e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0007870197296142578s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.3262958526611328s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.021379709243774414s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.000102996826171875s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 9.775161743164062e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 10.991252183914185s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.4345855712890625e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.3116757869720459s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.021080493927001953s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010132789611816406s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.0251998901367188e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 7.825279712677002s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 9.179115295410156e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.3028717041015625s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020779848098754883s
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.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.814697265625e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.0251998901367188e-05s
INFO | --- Analysis for BibSonomy took 8.784540891647339s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.749961853027344e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2878906726837158s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.1948089599609375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.049041748046875e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 8.543935298919678s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 5.2928924560546875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2978832721710205s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.218650817871094e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.2874603271484375e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 3.0049166679382324s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.8882951736450195s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006198883056640625s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 21.086552143096924s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.528092622756958s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 47.18951082229614s
Interoperability | New terms check for Bio2RDF::Affymetrix took 43.93122386932373s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.11468195915222s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.14206552505493164s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.5568068027496338s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.20256257057189941s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.316749095916748s
License | MR license check for Bio2RDF::Affymetrix took 0.43364810943603516s
License | HR license check for Bio2RDF::Affymetrix took 60.096800088882446s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.13609623908996582s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.232656002044678s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.39025378227233887s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13833999633789062s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.14380288124084473s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.1370234489440918s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.796039819717407s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 77.47295665740967s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.43815112113952637s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2609260082244873s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.7307775020599365s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.19666385650634766s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.1113440990447998s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2714111804962158s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.24176669120788574s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 110.69158983230591s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 12.393276691436768s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.28578925132751465s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.1698775291442871s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.11531758308410645s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.176941394805908s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8911869525909424s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.680121898651123s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.27059030532836914s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.27600598335266s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2483572959899902s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.225408315658569s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.2811758518218994s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.383405447006226s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7162413597106934s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3069489002227783s
Security | Sign check for Bio2RDF::Affymetrix took 0.12441205978393555s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 11.25907826423645s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.3600654602050781s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.021562814712524414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 12.689988613128662s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1042.5937974452972s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.489886999130249s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006809234619140625s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.658166885375977s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.220038652420044s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 45.36993360519409s
Interoperability | New terms check for Bio2RDF::Biomodels took 41.76318073272705s
Versatility | Languages check for Bio2RDF::Biomodels took 60.22551941871643s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2871074676513672s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.14533114433288574s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.44014978408813477s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.35284852981567383s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.4815731048583984s
License | MR license check for Bio2RDF::Biomodels took 0.4571354389190674s
License | HR license check for Bio2RDF::Biomodels took 60.24809145927429s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2512705326080322s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.11855149269104s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.6095860004425049s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.25760626792907715s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.27106595039367676s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.23567819595336914s
Performance | Throughput check for Bio2RDF::Biomodels took 11.25870156288147s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 75.79603481292725s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 1.4104118347167969s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3722231388092041s
Interlinking | skos check for Bio2RDF::Biomodels took 0.9077773094177246s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3544313907623291s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.27100372314453125s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5122818946838379s
Currency | Modification date check for Bio2RDF::Biomodels took 0.4996809959411621s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 110.6097354888916s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 13.24788522720337s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.42800188064575195s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.29941415786743164s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2984137535095215s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.201740026473999s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8969268798828125s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6551048755645752s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.45903944969177246s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.33223414421082s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.397977590560913s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.081654071807861s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3078956604003906s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.51458811759949s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7180960178375244s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4335606098175049s
Security | Sign check for Bio2RDF::Biomodels took 0.2830536365509033s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 10.16987919807434s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.5452511310577393s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011920928955078125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 12.70613956451416s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1044.316738128662s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.47545695304870605s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0005774497985839844s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.786237716674805s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2788724899291992s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.91363835334778s
Interoperability | New terms check for Bio2RDF::Bioportal took 42.69564390182495s
Versatility | Languages check for Bio2RDF::Bioportal took 60.25589895248413s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2755453586578369s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.15423035621643066s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.7792596817016602s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.30301403999328613s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.3702714443206787s
License | MR license check for Bio2RDF::Bioportal took 0.399280309677124s
License | HR license check for Bio2RDF::Bioportal took 60.24704933166504s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2664055824279785s
Understandability | Number of label check for Bio2RDF::Bioportal took 9.726328372955322s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6230659484863281s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2581675052642822s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.27539587020874023s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.27953600883483887s
Performance | Throughput check for Bio2RDF::Bioportal took 11.253448486328125s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 75.5433189868927s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.6058750152587891s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.34342050552368164s
Interlinking | skos check for Bio2RDF::Bioportal took 0.7255818843841553s
Interlinking | skos check for Bio2RDF::Bioportal took 0.3585629463195801s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.26616644859313965s
Currency | Creation date check for Bio2RDF::Bioportal took 0.49693870544433594s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5014538764953613s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 110.27346062660217s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 13.415481567382812s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.43305158615112305s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2656567096710205s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.27038145065307617s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.87749457359314s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8873872756958008s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6511802673339844s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.47524309158325195s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.42930936813354s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.3976922035217285s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.312805891036987s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.2755558490753174s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.54792904853821s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7241816520690918s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.4107015132904053s
Security | Sign check for Bio2RDF::Bioportal took 0.2784278392791748s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 11.112385034561157s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.45177555084228516s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00043773651123046875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 12.797188997268677s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1051.9648411273956s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.14374399185180664s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.20621418952941895s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.02253580093383789s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0009050369262695312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 6.365776062011719e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-chembl took 16.72102165222168s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.4690988063812256s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.000629425048828125s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 20.025400400161743s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.181156873703003s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 46.25208568572998s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 42.49597430229187s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.257554054260254s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2934718132019043s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15595054626464844s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.6771199703216553s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.3401176929473877s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.2245683670043945s
License | MR license check for Bio2RDF::Clinicaltrials took 0.51239013671875s
License | HR license check for Bio2RDF::Clinicaltrials took 60.24061465263367s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 1.3119792938232422s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.116531610488892s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 5.109943628311157s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.26912713050842285s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2629241943359375s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.27747201919555664s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.756164789199829s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 77.0625913143158s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.6141057014465332s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3279998302459717s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7153682708740234s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3315098285675049s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2733268737792969s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5267462730407715s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5001852512359619s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 110.96065139770508s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 12.861933946609497s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.428861141204834s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.28330564498901367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.28162240982055664s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 7.541617393493652s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8893928527832031s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6638474464416504s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.4507420063018799s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.32324647903442s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.3811542987823486s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.420496463775635s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3167674541473389s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.580371379852295s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7263529300689697s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4523906707763672s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.25365185737609863s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 10.179795503616333s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.45197200775146484s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.021075963973999023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 12.688250064849854s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1050.6364176273346s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.4765760898590088s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005908012390136719s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.116831302642822s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2702593803405762s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.61678194999695s
Interoperability | New terms check for Bio2RDF::Ctd took 42.40137529373169s
Versatility | Languages check for Bio2RDF::Ctd took 60.23635482788086s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2880525588989258s
Security | Check HTTPS for Bio2RDF::Ctd took 0.16565585136413574s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.4622535705566406s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.30162978172302246s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.4060628414154053s
License | MR license check for Bio2RDF::Ctd took 0.4653811454772949s
License | HR license check for Bio2RDF::Ctd took 60.26326894760132s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.24811720848083496s
Understandability | Number of label check for Bio2RDF::Ctd took 10.036365985870361s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5908377170562744s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2612907886505127s
Verifiability | Authors check for Bio2RDF::Ctd took 0.2707960605621338s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.26888322830200195s
Performance | Throughput check for Bio2RDF::Ctd took 11.431621789932251s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 76.52747583389282s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.584148645401001s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3707129955291748s
Interlinking | skos check for Bio2RDF::Ctd took 0.8221986293792725s
Interlinking | skos check for Bio2RDF::Ctd took 0.3537101745605469s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.25016331672668457s
Currency | Creation date check for Bio2RDF::Ctd took 0.5207648277282715s
Currency | Modification date check for Bio2RDF::Ctd took 0.5259284973144531s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 109.6242344379425s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 15.098421335220337s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4536590576171875s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2885775566101074s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2829585075378418s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.6360180377960205s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8809843063354492s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6421360969543457s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.4356203079223633s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.42416548728943s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.386942148208618s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.835022926330566s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3078584671020508s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.54175639152527s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7225279808044434s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.43445253372192383s
Security | Sign check for Bio2RDF::Ctd took 0.27837181091308594s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.262928485870361s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.4632706642150879s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.461143493652344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 13.174625158309937s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-ctd took 1058.297105550766s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 9.369850158691406e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0012333393096923828s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.32062649726867676s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021956682205200195s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.173683166503906e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.930750846862793s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.4896411895751953s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005564689636230469s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 19.17615056037903s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.292423963546753s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 53.332014083862305s
Interoperability | New terms check for Bio2RDF::Dbsnp took 44.59050679206848s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.256441831588745s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.27277135848999023s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1675090789794922s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.5245823860168457s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.34361743927001953s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.394808292388916s
License | MR license check for Bio2RDF::Dbsnp took 0.44325900077819824s
License | HR license check for Bio2RDF::Dbsnp took 60.24911189079285s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2740628719329834s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.27508282661438s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5836548805236816s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2570028305053711s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2551307678222656s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.2743101119995117s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.466972351074219s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 77.11417770385742s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.6258444786071777s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3619804382324219s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.9643552303314209s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.37729978561401367s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2550995349884033s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5197887420654297s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5062177181243896s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 112.12635827064514s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 12.042551040649414s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.43677544593811035s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2597789764404297s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.25081515312194824s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.200837850570679s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8918523788452148s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6649594306945801s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.38494420051574707s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.57341432571411s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.373267650604248s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.3732709884643555s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.30999755859375s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.55052614212036s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7217416763305664s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.44089293479919434s
Security | Sign check for Bio2RDF::Dbsnp took 0.26082658767700195s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 16.635495901107788s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.5067102909088135s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 12.203846454620361s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1060.955243587494s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.458406925201416s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005769729614257812s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 20.63118004798889s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2040164470672607s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 48.649614334106445s
Interoperability | New terms check for Bio2RDF::Drugbank took 45.38471055030823s
Versatility | Languages check for Bio2RDF::Drugbank took 60.23608660697937s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2559847831726074s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.16214275360107422s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.6096024513244629s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.32001423835754395s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.322033643722534s
License | MR license check for Bio2RDF::Drugbank took 0.5929629802703857s
License | HR license check for Bio2RDF::Drugbank took 60.257330656051636s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.23991036415100098s
Understandability | Number of label check for Bio2RDF::Drugbank took 0.24718308448791504s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.48714160919189453s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2461385726928711s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.24251842498779297s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2579677104949951s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 0.00013208389282226562s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.25156569480895996s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.259340763092041s
Interlinking | skos check for Bio2RDF::Drugbank took 0.24558424949645996s
Interlinking | skos check for Bio2RDF::Drugbank took 0.2360854148864746s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.25861239433288574s
Currency | Creation date check for Bio2RDF::Drugbank took 0.48369622230529785s
Currency | Modification date check for Bio2RDF::Drugbank took 0.47609829902648926s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 1.8067986965179443s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.24748015403747559s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6583547592163086s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.2472972869873047s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 0.2362198829650879s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 1.53513765335083s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7173683643341064s
Security | Sign check for Bio2RDF::Drugbank took 0.2397618293762207s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 11.664620161056519s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.4055356979370117s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020815134048461914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0006785392761230469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 9.5367431640625e-07s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-drugbank took 483.07366847991943s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.44963836669921875s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006008148193359375s
Extra | Recovery of all triples for Bio2RDF::Genage took 19.886844635009766s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.247673511505127s
Amount of data | Number of triples check for Bio2RDF::Genage took 46.4999635219574s
Interoperability | New terms check for Bio2RDF::Genage took 41.419464349746704s
Versatility | Languages check for Bio2RDF::Genage took 60.23930764198303s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.3020651340484619s
Security | Check HTTPS for Bio2RDF::Genage took 0.14458322525024414s
Interpretability | RDF structures check for Bio2RDF::Genage took 1.0561676025390625s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.34281277656555176s
Availability | RDF dump link check for Bio2RDF::Genage took 2.417072057723999s
License | MR license check for Bio2RDF::Genage took 0.48877668380737305s
License | HR license check for Bio2RDF::Genage took 60.236987829208374s
Amount of data | Number of property check for Bio2RDF::Genage took 0.3099193572998047s
Understandability | Number of label check for Bio2RDF::Genage took 9.802088499069214s
Understandability | URI regex check for Bio2RDF::Genage took 0.5894961357116699s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2739222049713135s
Verifiability | Authors check for Bio2RDF::Genage took 0.2633020877838135s
Verifiability | Publishers check for Bio2RDF::Genage took 0.24468350410461426s
Performance | Throughput check for Bio2RDF::Genage took 11.337969064712524s
Amount of data | Check the number of entities for Bio2RDF::Genage took 77.29378867149353s
Verifiability | Contribs. check for Bio2RDF::Genage took 2.0087480545043945s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.36959338188171387s
Interlinking | skos check for Bio2RDF::Genage took 0.9408042430877686s
Interlinking | skos check for Bio2RDF::Genage took 0.34688329696655273s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.26203393936157227s
Currency | Creation date check for Bio2RDF::Genage took 0.5163540840148926s
Currency | Modification date check for Bio2RDF::Genage took 0.5123672485351562s
Rep.Conc. | URIs length for Bio2RDF::Genage took 109.70401215553284s
Interoperability | New vocabularies check for Bio2RDF::Genage took 13.01097822189331s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.45840024948120117s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2889373302459717s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.26000475883483887s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.266856908798218s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8892414569854736s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6548802852630615s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.43039369583129883s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 64.98016405105591s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.349634885787964s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.521578550338745s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.2739410400390625s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.53269100189209s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7252650260925293s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.45124173164367676s
Security | Sign check for Bio2RDF::Genage took 0.2844555377960205s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 18.472561359405518s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.42682790756225586s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.29425048828125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 14.133999347686768s
Believability | Calculation of trust value for Bio2RDF::Genage took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-genage took 1058.6723670959473s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.4894692897796631s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0005991458892822266s
Extra | Recovery of all triples for Bio2RDF::Gendr took 19.545795917510986s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2506074905395508s
Amount of data | Number of triples check for Bio2RDF::Gendr took 48.716681718826294s
Interoperability | New terms check for Bio2RDF::Gendr took 44.3520827293396s
Versatility | Languages check for Bio2RDF::Gendr took 60.27751159667969s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2767183780670166s
Security | Check HTTPS for Bio2RDF::Gendr took 0.14495396614074707s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.7504017353057861s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.39195799827575684s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.1943700313568115s
License | MR license check for Bio2RDF::Gendr took 0.5292487144470215s
License | HR license check for Bio2RDF::Gendr took 60.26733350753784s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2592012882232666s
Understandability | Number of label check for Bio2RDF::Gendr took 10.322334289550781s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5618979930877686s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.25872135162353516s
Verifiability | Authors check for Bio2RDF::Gendr took 0.262542724609375s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.24953460693359375s
Performance | Throughput check for Bio2RDF::Gendr took 11.434024810791016s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 76.96815609931946s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.5838890075683594s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.32881712913513184s
Interlinking | skos check for Bio2RDF::Gendr took 0.7041034698486328s
Interlinking | skos check for Bio2RDF::Gendr took 0.35971975326538086s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.27886152267456055s
Currency | Creation date check for Bio2RDF::Gendr took 0.5040254592895508s
Currency | Modification date check for Bio2RDF::Gendr took 0.5170938968658447s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 113.18557620048523s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 12.887462615966797s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4269876480102539s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.280043363571167s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.24422287940979004s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.2269909381866455s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8936305046081543s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6505284309387207s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.3935732841491699s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.40294122695923s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.371678590774536s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.230118989944458s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.2733383178710938s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.48638081550598s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7269365787506104s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.4270014762878418s
Security | Sign check for Bio2RDF::Gendr took 0.34592103958129883s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 10.805702447891235s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.4639902114868164s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 13.655356407165527s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-gendr took 1052.7021548748016s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.48197197914123535s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006213188171386719s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.332741498947144s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2469112873077393s
Amount of data | Number of triples check for Bio2RDF::Goa took 46.14313268661499s
Interoperability | New terms check for Bio2RDF::Goa took 42.03801083564758s
Versatility | Languages check for Bio2RDF::Goa took 60.246835708618164s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.2729971408843994s
Security | Check HTTPS for Bio2RDF::Goa took 0.15612483024597168s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.5792036056518555s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3403925895690918s
Availability | RDF dump link check for Bio2RDF::Goa took 2.3675901889801025s
License | MR license check for Bio2RDF::Goa took 0.3571889400482178s
License | HR license check for Bio2RDF::Goa took 60.23852038383484s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2770965099334717s
Understandability | Number of label check for Bio2RDF::Goa took 9.766257762908936s
Understandability | URI regex check for Bio2RDF::Goa took 0.593468189239502s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2733299732208252s
Verifiability | Authors check for Bio2RDF::Goa took 0.269010066986084s
Verifiability | Publishers check for Bio2RDF::Goa took 0.25721216201782227s
Performance | Throughput check for Bio2RDF::Goa took 11.909642457962036s
Amount of data | Check the number of entities for Bio2RDF::Goa took 76.16354393959045s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.6035270690917969s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3615262508392334s
Interlinking | skos check for Bio2RDF::Goa took 0.781883716583252s
Interlinking | skos check for Bio2RDF::Goa took 0.4458582401275635s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.28034472465515137s
Currency | Creation date check for Bio2RDF::Goa took 0.5184850692749023s
Currency | Modification date check for Bio2RDF::Goa took 0.4892909526824951s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.28165531158447s
Interoperability | New vocabularies check for Bio2RDF::Goa took 13.023361682891846s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.43593478202819824s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2734391689300537s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.2541830539703369s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 6.975064992904663s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.887554407119751s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6561012268066406s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4050168991088867s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.38264560699463s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.3969311714172363s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.370157480239868s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.2782583236694336s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.51330876350403s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7347562313079834s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.43608951568603516s
Security | Sign check for Bio2RDF::Goa took 0.27134275436401367s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 10.393316268920898s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.5077304840087891s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 12.776061773300171s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-goa took 1049.4759290218353s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.45986342430114746s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0005733966827392578s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 20.15254783630371s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2187082767486572s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 46.21068620681763s
Interoperability | New terms check for Bio2RDF::Hgnc took 42.617382526397705s
Versatility | Languages check for Bio2RDF::Hgnc took 60.23028540611267s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2937583923339844s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15386152267456055s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.8610658645629883s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3128046989440918s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.449711799621582s
License | MR license check for Bio2RDF::Hgnc took 0.3979172706604004s
License | HR license check for Bio2RDF::Hgnc took 60.25787687301636s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.29602956771850586s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.942097187042236s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5796875953674316s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.267427921295166s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.28405141830444336s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.26358938217163086s
Performance | Throughput check for Bio2RDF::Hgnc took 11.679332494735718s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 77.21016359329224s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 1.418731689453125s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3620448112487793s
Interlinking | skos check for Bio2RDF::Hgnc took 0.8450274467468262s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3532893657684326s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2822902202606201s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5442030429840088s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5392217636108398s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.34455251693726s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 15.035342931747437s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.41996312141418457s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2934989929199219s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2507500648498535s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.572664022445679s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8900079727172852s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6651079654693604s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4186127185821533s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.28617286682129s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.3761167526245117s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.669539928436279s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3129241466522217s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.54541516304016s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7416253089904785s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4023926258087158s
Security | Sign check for Bio2RDF::Hgnc took 0.27970075607299805s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 10.07636308670044s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.5329728126525879s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010561943054199219s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 13.204233646392822s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1045.7195482254028s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.4752311706542969s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006556510925292969s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.0159969329834s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2292468547821045s
Amount of data | Number of triples check for Bio2RDF::Homologene took 46.44344401359558s
Interoperability | New terms check for Bio2RDF::Homologene took 43.22547197341919s
Versatility | Languages check for Bio2RDF::Homologene took 60.25172281265259s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.26137375831604004s
Security | Check HTTPS for Bio2RDF::Homologene took 0.15493392944335938s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.6682264804840088s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.3518509864807129s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.439744234085083s
License | MR license check for Bio2RDF::Homologene took 0.37295985221862793s
License | HR license check for Bio2RDF::Homologene took 60.24214434623718s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.2519359588623047s
Understandability | Number of label check for Bio2RDF::Homologene took 10.297925472259521s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5873425006866455s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.25430917739868164s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2498316764831543s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2697575092315674s
Performance | Throughput check for Bio2RDF::Homologene took 11.242254257202148s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 80.49724984169006s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.5796346664428711s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.3635067939758301s
Interlinking | skos check for Bio2RDF::Homologene took 0.7246921062469482s
Interlinking | skos check for Bio2RDF::Homologene took 0.3566586971282959s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.2706615924835205s
Currency | Creation date check for Bio2RDF::Homologene took 0.5232043266296387s
Currency | Modification date check for Bio2RDF::Homologene took 0.4884517192840576s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 109.53208708763123s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 13.550817012786865s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4283933639526367s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2954738140106201s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.28194165229797363s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.2288641929626465s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8918778896331787s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6751358509063721s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.41741442680358887s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.57286286354065s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.414564847946167s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.6205291748046875s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3208801746368408s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.55299162864685s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.753516674041748s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.46047091484069824s
Security | Sign check for Bio2RDF::Homologene took 0.2795584201812744s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 10.39212965965271s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.29718661308288574s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 12.714617729187012s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-homologene took 1049.4651358127594s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.4723520278930664s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0007300376892089844s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.831525802612305s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2357158660888672s
Amount of data | Number of triples check for Bio2RDF::Interpro took 47.10582995414734s
Interoperability | New terms check for Bio2RDF::Interpro took 41.888492822647095s
Versatility | Languages check for Bio2RDF::Interpro took 60.25762891769409s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2761564254760742s
Security | Check HTTPS for Bio2RDF::Interpro took 0.15371060371398926s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.5540156364440918s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.359316349029541s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.2457082271575928s
License | MR license check for Bio2RDF::Interpro took 0.48020076751708984s
License | HR license check for Bio2RDF::Interpro took 60.24563765525818s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.36434459686279297s
Understandability | Number of label check for Bio2RDF::Interpro took 9.81705093383789s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5954618453979492s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2664031982421875s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2758193016052246s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.26380443572998047s
Performance | Throughput check for Bio2RDF::Interpro took 10.368979215621948s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 76.56982946395874s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.614875078201294s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.3417689800262451s
Interlinking | skos check for Bio2RDF::Interpro took 1.0708708763122559s
Interlinking | skos check for Bio2RDF::Interpro took 0.3618180751800537s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2622029781341553s
Currency | Creation date check for Bio2RDF::Interpro took 0.5198702812194824s
Currency | Modification date check for Bio2RDF::Interpro took 0.511345386505127s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 109.7800612449646s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 12.900179624557495s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.410311222076416s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.26146936416625977s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2837085723876953s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.852845191955566s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8873839378356934s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6659691333770752s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.3682570457458496s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.3121542930603s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.3726227283477783s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.518279075622559s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.2762386798858643s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.563825368881226s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.746382474899292s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.40062832832336426s
Security | Sign check for Bio2RDF::Interpro took 0.27442073822021484s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 10.829783916473389s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.42215394973754883s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00011086463928222656s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 12.272125244140625s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-interpro took 1040.4227061271667s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.137315034866333s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.32943034172058105s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.021242141723632812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.700920104980469e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-iproclass took 17.028958559036255s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 1.265202283859253s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006415843963623047s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.867228269577026s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2787909507751465s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 46.210262060165405s
Interoperability | New terms check for Bio2RDF::Irefindex took 41.66411209106445s
Versatility | Languages check for Bio2RDF::Irefindex took 60.233529806137085s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.26729440689086914s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15745759010314941s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.6609408855438232s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.32266831398010254s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.4114251136779785s
License | MR license check for Bio2RDF::Irefindex took 0.6534888744354248s
License | HR license check for Bio2RDF::Irefindex took 60.24774146080017s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2529881000518799s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.323798656463623s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5697205066680908s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2788257598876953s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2574656009674072s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.24747228622436523s
Performance | Throughput check for Bio2RDF::Irefindex took 11.234519958496094s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 77.7295651435852s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6161344051361084s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.33998847007751465s
Interlinking | skos check for Bio2RDF::Irefindex took 0.7140932083129883s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3215639591217041s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.27277588844299316s
Currency | Creation date check for Bio2RDF::Irefindex took 0.49176812171936035s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5186879634857178s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 110.84505200386047s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 13.803413391113281s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4262723922729492s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.26416945457458496s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.2542850971221924s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.117208003997803s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8893113136291504s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6700546741485596s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.3899214267730713s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.42382955551147s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.4130303859710693s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.244909286499023s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.2817091941833496s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.51427865028381s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7168982028961182s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4293026924133301s
Security | Sign check for Bio2RDF::Irefindex took 0.270810604095459s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 10.407357454299927s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.4980130195617676s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.987022399902344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 11.785628318786621s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1046.5606141090393s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13983845710754395s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2900245189666748s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.457069396972656e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 9.572134017944336s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.47505879402160645s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005991458892822266s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.85738515853882s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2823734283447266s
Amount of data | Number of triples check for Bio2RDF::Lsr took 46.1299774646759s
Interoperability | New terms check for Bio2RDF::Lsr took 41.174681425094604s
Versatility | Languages check for Bio2RDF::Lsr took 60.24455142021179s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.28247904777526855s
Security | Check HTTPS for Bio2RDF::Lsr took 0.15578246116638184s
Interpretability | RDF structures check for Bio2RDF::Lsr took 1.0300536155700684s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.34925127029418945s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.254754066467285s
License | MR license check for Bio2RDF::Lsr took 0.4577610492706299s
License | HR license check for Bio2RDF::Lsr took 60.25557613372803s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.27496838569641113s
Understandability | Number of label check for Bio2RDF::Lsr took 10.442806959152222s
Understandability | URI regex check for Bio2RDF::Lsr took 0.571674108505249s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.25577759742736816s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2759106159210205s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.24933266639709473s
Performance | Throughput check for Bio2RDF::Lsr took 11.280125617980957s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 78.67484617233276s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.6918368339538574s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.37537264823913574s
Interlinking | skos check for Bio2RDF::Lsr took 0.858466625213623s
Interlinking | skos check for Bio2RDF::Lsr took 0.37345075607299805s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.27338480949401855s
Currency | Creation date check for Bio2RDF::Lsr took 0.5235610008239746s
Currency | Modification date check for Bio2RDF::Lsr took 0.516176700592041s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 109.93346095085144s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 13.370707273483276s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4539504051208496s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.25815701484680176s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2954723834991455s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.085619688034058s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8809287548065186s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6614787578582764s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.39090871810913086s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.04025602340698s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.3335459232330322s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.602003335952759s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.2792754173278809s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.55670499801636s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7302360534667969s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.45766615867614746s
Security | Sign check for Bio2RDF::Lsr took 0.2656421661376953s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 10.00179409980774s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.5156025886535645s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020996809005737305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.054473876953125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 13.18569016456604s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-lsr took 1043.3876893520355s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.47405147552490234s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006301403045654297s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.567447900772095s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.228379249572754s
Amount of data | Number of triples check for Bio2RDF::Mesh took 46.020262241363525s
Interoperability | New terms check for Bio2RDF::Mesh took 44.010841846466064s
Versatility | Languages check for Bio2RDF::Mesh took 60.22590470314026s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.2723550796508789s
Security | Check HTTPS for Bio2RDF::Mesh took 0.1534433364868164s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.7939553260803223s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.3461639881134033s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.44950795173645s
License | MR license check for Bio2RDF::Mesh took 0.3575928211212158s
License | HR license check for Bio2RDF::Mesh took 60.260571002960205s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.3124723434448242s
Understandability | Number of label check for Bio2RDF::Mesh took 10.729677677154541s
Understandability | URI regex check for Bio2RDF::Mesh took 0.6086544990539551s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.26049041748046875s
Verifiability | Authors check for Bio2RDF::Mesh took 0.25571775436401367s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2563297748565674s
Performance | Throughput check for Bio2RDF::Mesh took 11.518675565719604s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 73.81034326553345s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.571375846862793s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.37174034118652344s
Interlinking | skos check for Bio2RDF::Mesh took 1.055314540863037s
Interlinking | skos check for Bio2RDF::Mesh took 0.36078596115112305s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2606654167175293s
Currency | Creation date check for Bio2RDF::Mesh took 0.5115635395050049s
Currency | Modification date check for Bio2RDF::Mesh took 0.5231750011444092s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 114.77253699302673s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 12.524718999862671s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.41722869873046875s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2707486152648926s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.308483362197876s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.39750599861145s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.891770601272583s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6615276336669922s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4472849369049072s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.52102661132812s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.396481990814209s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.204220294952393s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3127589225769043s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.54507827758789s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7148947715759277s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.43203210830688477s
Security | Sign check for Bio2RDF::Mesh took 0.2598855495452881s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 10.530691146850586s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.5457029342651367s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02027130126953125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 6.723403930664062e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 11.468209743499756s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-mesh took 1050.2692580223083s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.470226526260376s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006220340728759766s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.505510568618774s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2274999618530273s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.96437621116638s
Interoperability | New terms check for Bio2RDF::Mgi took 41.38313937187195s
Versatility | Languages check for Bio2RDF::Mgi took 60.2356173992157s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.29126405715942383s
Security | Check HTTPS for Bio2RDF::Mgi took 0.16179132461547852s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.7065165042877197s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.31885600090026855s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.267071485519409s
License | MR license check for Bio2RDF::Mgi took 0.3835630416870117s
License | HR license check for Bio2RDF::Mgi took 60.230151891708374s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.27567315101623535s
Understandability | Number of label check for Bio2RDF::Mgi took 9.785776138305664s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5750560760498047s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.25107812881469727s
Verifiability | Authors check for Bio2RDF::Mgi took 0.25307679176330566s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2598273754119873s
Performance | Throughput check for Bio2RDF::Mgi took 11.217170476913452s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 75.72063446044922s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.74094557762146s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.3786001205444336s
Interlinking | skos check for Bio2RDF::Mgi took 0.9051940441131592s
Interlinking | skos check for Bio2RDF::Mgi took 0.36621546745300293s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.27117395401000977s
Currency | Creation date check for Bio2RDF::Mgi took 0.5157830715179443s
Currency | Modification date check for Bio2RDF::Mgi took 0.5249216556549072s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 109.72386574745178s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 12.1408212184906s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.4883711338043213s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2786829471588135s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.28021907806396484s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 6.799084186553955s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8880627155303955s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6584916114807129s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.43097734451293945s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.402841091156s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4519827365875244s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 5.982247352600098s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.2811572551727295s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.52197742462158s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7255446910858154s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.4431416988372803s
Security | Sign check for Bio2RDF::Mgi took 0.2567300796508789s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 10.748852014541626s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.43688344955444336s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.1552734375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 12.745378971099854s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-mgi took 1040.148012638092s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.48367786407470703s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0007121562957763672s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.740832805633545s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.247222661972046s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 46.6121141910553s
Interoperability | New terms check for Bio2RDF::Ncbigene took 43.17334008216858s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.24600625038147s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.29260826110839844s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.16851186752319336s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.544156551361084s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3313603401184082s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.204005241394043s
License | MR license check for Bio2RDF::Ncbigene took 0.4900665283203125s
License | HR license check for Bio2RDF::Ncbigene took 60.24219512939453s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2696802616119385s
Understandability | Number of label check for Bio2RDF::Ncbigene took 10.808883905410767s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.6081466674804688s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.26112914085388184s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2754230499267578s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.24532485008239746s
Performance | Throughput check for Bio2RDF::Ncbigene took 10.846183061599731s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 77.46992611885071s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.5773608684539795s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3365206718444824s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.9870028495788574s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3295128345489502s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2725036144256592s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5144374370574951s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5189540386199951s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 115.32163381576538s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 12.820032119750977s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.478621244430542s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2681694030761719s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.279094934463501s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.441314458847046s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8900485038757324s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6566483974456787s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.4005279541015625s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.67599630355835s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.3902640342712402s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.980872869491577s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3091492652893066s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.54624390602112s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7419278621673584s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.44051671028137207s
Security | Sign check for Bio2RDF::Ncbigene took 0.2759993076324463s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 10.464622974395752s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.4932980537414551s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.0001232624053955078s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 12.630028247833252s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1059.9158799648285s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.4747169017791748s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006461143493652344s
Extra | Recovery of all triples for Bio2RDF::Ndc took 19.00237226486206s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.208611249923706s
Amount of data | Number of triples check for Bio2RDF::Ndc took 46.31222939491272s
Interoperability | New terms check for Bio2RDF::Ndc took 41.263306856155396s
Versatility | Languages check for Bio2RDF::Ndc took 60.247207164764404s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.28417372703552246s
Security | Check HTTPS for Bio2RDF::Ndc took 0.1445760726928711s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.8521416187286377s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.3356349468231201s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.277156114578247s
License | MR license check for Bio2RDF::Ndc took 0.50868821144104s
License | HR license check for Bio2RDF::Ndc took 60.25964593887329s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2764885425567627s
Understandability | Number of label check for Bio2RDF::Ndc took 10.51095199584961s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5811476707458496s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.27990126609802246s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2835509777069092s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.27276134490966797s
Performance | Throughput check for Bio2RDF::Ndc took 10.74150276184082s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 78.95098090171814s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.5745441913604736s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.3216257095336914s
Interlinking | skos check for Bio2RDF::Ndc took 0.6621115207672119s
Interlinking | skos check for Bio2RDF::Ndc took 0.3346385955810547s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2681896686553955s
Currency | Creation date check for Bio2RDF::Ndc took 0.5387661457061768s
Currency | Modification date check for Bio2RDF::Ndc took 0.48618435859680176s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 108.83022737503052s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 13.138023614883423s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.47692227363586426s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2641112804412842s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2512693405151367s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 6.738622188568115s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.887763500213623s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6722185611724854s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.4043881893157959s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.43567776679993s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.3764376640319824s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.611753225326538s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.317791223526001s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.55672550201416s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7545864582061768s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.4283742904663086s
Security | Sign check for Bio2RDF::Ndc took 0.2741072177886963s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 9.950552940368652s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.5449070930480957s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 12.334396839141846s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-ndc took 1046.844467639923s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13831281661987305s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2726626396179199s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.022176504135131836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.457069396972656e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.6815757751464844s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4740602970123291s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006532669067382812s
Extra | Recovery of all triples for Bio2RDF::Omim took 21.640539169311523s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2538151741027832s
Amount of data | Number of triples check for Bio2RDF::Omim took 47.703362226486206s
Interoperability | New terms check for Bio2RDF::Omim took 42.84176969528198s
Versatility | Languages check for Bio2RDF::Omim took 60.24548554420471s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.3215973377227783s
Security | Check HTTPS for Bio2RDF::Omim took 0.17980194091796875s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.791473388671875s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.33756136894226074s
Availability | RDF dump link check for Bio2RDF::Omim took 2.4650893211364746s
License | MR license check for Bio2RDF::Omim took 0.5068161487579346s
License | HR license check for Bio2RDF::Omim took 60.26364493370056s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2673988342285156s
Understandability | Number of label check for Bio2RDF::Omim took 10.311167240142822s
Understandability | URI regex check for Bio2RDF::Omim took 0.6202852725982666s
Understandability | Vocabs check for Bio2RDF::Omim took 0.26398730278015137s
Verifiability | Authors check for Bio2RDF::Omim took 0.26442408561706543s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2650883197784424s
Performance | Throughput check for Bio2RDF::Omim took 10.504786729812622s
Amount of data | Check the number of entities for Bio2RDF::Omim took 82.36126899719238s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.5806803703308105s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3618030548095703s
Interlinking | skos check for Bio2RDF::Omim took 0.8168919086456299s
Interlinking | skos check for Bio2RDF::Omim took 0.361541748046875s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2642548084259033s
Currency | Creation date check for Bio2RDF::Omim took 0.5145161151885986s
Currency | Modification date check for Bio2RDF::Omim took 0.5305948257446289s
Rep.Conc. | URIs length for Bio2RDF::Omim took 112.39311599731445s
Interoperability | New vocabularies check for Bio2RDF::Omim took 11.79626178741455s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.46329569816589355s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.28136658668518066s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2651073932647705s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.890372276306152s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8850493431091309s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6628556251525879s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.42656898498535156s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.86349558830261s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.397623300552368s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 11.50734281539917s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.300574779510498s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.574583292007446s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7405695915222168s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.4377150535583496s
Security | Sign check for Bio2RDF::Omim took 0.265575647354126s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 10.296181917190552s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.9043087959289551s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013446807861328125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 12.704020500183105s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-omim took 1060.8950543403625s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 0.00010704994201660156s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2972850799560547s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.981590270996094e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 2.9258320331573486s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.4670851230621338s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006248950958251953s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 20.107128381729126s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.1980969905853271s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.5104033946991s
Interoperability | New terms check for Bio2RDF::Orphanet took 42.03765940666199s
Versatility | Languages check for Bio2RDF::Orphanet took 60.238600969314575s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.30162668228149414s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.14566612243652344s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.6814048290252686s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.2988440990447998s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.1079211235046387s
License | MR license check for Bio2RDF::Orphanet took 0.5160646438598633s
License | HR license check for Bio2RDF::Orphanet took 60.261147022247314s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.27643370628356934s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.185852289199829s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5752191543579102s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2442948818206787s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2649393081665039s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2711789608001709s
Performance | Throughput check for Bio2RDF::Orphanet took 11.365702152252197s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 77.26201438903809s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.5847175121307373s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.36562275886535645s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7132244110107422s
Interlinking | skos check for Bio2RDF::Orphanet took 0.3517894744873047s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.26442956924438477s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5079596042633057s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5058126449584961s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 112.40546488761902s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 12.450883626937866s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4772522449493408s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2940964698791504s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.276702880859375s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.994399785995483s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8828527927398682s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6659891605377197s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.42876672744750977s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.02415823936462s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.377256393432617s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 7.062387704849243s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3214213848114014s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.63777422904968s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7318453788757324s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.45929622650146484s
Security | Sign check for Bio2RDF::Orphanet took 0.2659578323364258s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 10.729446172714233s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.4176795482635498s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02064800262451172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.249282836914062e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 12.906585693359375s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1051.1537866592407s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13899445533752441s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.30768656730651855s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.02274346351623535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.294419765472412s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.47349023818969727s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005514621734619141s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.786990642547607s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2328732013702393s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 46.0450074672699s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 41.698981523513794s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.248905420303345s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.3168058395385742s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16739439964294434s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.8612332344055176s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.3268136978149414s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.4783802032470703s
License | MR license check for Bio2RDF::Pharmgkb took 0.4830620288848877s
License | HR license check for Bio2RDF::Pharmgkb took 60.22935914993286s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2580530643463135s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.48028826713562s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.591355562210083s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2658557891845703s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2625277042388916s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.25196146965026855s
Performance | Throughput check for Bio2RDF::Pharmgkb took 10.729670524597168s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 79.94412732124329s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.574066162109375s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.39542484283447266s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.875840425491333s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.34697818756103516s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2753148078918457s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5097532272338867s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.505016565322876s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 110.1163420677185s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 12.826809883117676s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.46042513847351074s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2918374538421631s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.27213335037231445s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.66069221496582s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8965244293212891s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6687679290771484s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4147624969482422s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.05252170562744s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.3784971237182617s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.129909038543701s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.397993564605713s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.60986661911011s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7315130233764648s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4203331470489502s
Security | Sign check for Bio2RDF::Pharmgkb took 0.2644312381744385s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 10.161372661590576s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.4563300609588623s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 6.937980651855469e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 12.306796312332153s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1052.1897628307343s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.47386980056762695s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006763935089111328s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.55868124961853s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2677829265594482s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 45.75877070426941s
Interoperability | New terms check for Bio2RDF::Pubmed took 42.62752032279968s
Versatility | Languages check for Bio2RDF::Pubmed took 60.247573137283325s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.27161622047424316s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.1700429916381836s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.6687119007110596s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3059251308441162s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.4590091705322266s
License | MR license check for Bio2RDF::Pubmed took 0.4309070110321045s
License | HR license check for Bio2RDF::Pubmed took 60.23872923851013s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.29337406158447266s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.722867965698242s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5803720951080322s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2633476257324219s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.26830363273620605s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.25623202323913574s
Performance | Throughput check for Bio2RDF::Pubmed took 11.671696901321411s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 76.1973340511322s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.5853323936462402s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.33438730239868164s
Interlinking | skos check for Bio2RDF::Pubmed took 0.7590398788452148s
Interlinking | skos check for Bio2RDF::Pubmed took 0.39638376235961914s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2743399143218994s
Currency | Creation date check for Bio2RDF::Pubmed took 0.495898962020874s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5136730670928955s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 110.50085234642029s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 11.829554796218872s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.4321596622467041s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.260312557220459s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2667562961578369s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.487085342407227s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8863530158996582s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6602263450622559s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.3928985595703125s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.76100468635559s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.372702121734619s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.215365886688232s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.4143226146697998s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.546653509140015s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7180702686309814s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.4107701778411865s
Security | Sign check for Bio2RDF::Pubmed took 0.2751739025115967s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 10.256056547164917s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.5532803535461426s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014019012451171875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 12.348310708999634s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1043.1134595870972s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.14246535301208496s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.29633188247680664s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.82012939453125e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-sabiork took 9.41927433013916s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.47539258003234863s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005240440368652344s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.961385250091553s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2196753025054932s
Amount of data | Number of triples check for Bio2RDF::Sgd took 46.104875326156616s
Interoperability | New terms check for Bio2RDF::Sgd took 43.049219846725464s
Versatility | Languages check for Bio2RDF::Sgd took 60.25769281387329s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.3045332431793213s
Security | Check HTTPS for Bio2RDF::Sgd took 0.1453080177307129s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.5810520648956299s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.31316113471984863s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.397731304168701s
License | MR license check for Bio2RDF::Sgd took 0.434556245803833s
License | HR license check for Bio2RDF::Sgd took 60.23736548423767s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2505486011505127s
Understandability | Number of label check for Bio2RDF::Sgd took 10.341794490814209s
Understandability | URI regex check for Bio2RDF::Sgd took 0.549907922744751s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2563788890838623s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2816770076751709s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.27092862129211426s
Performance | Throughput check for Bio2RDF::Sgd took 11.638619899749756s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 75.47802472114563s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5520081520080566s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.34859442710876465s
Interlinking | skos check for Bio2RDF::Sgd took 0.784806489944458s
Interlinking | skos check for Bio2RDF::Sgd took 0.34458017349243164s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.25805044174194336s
Currency | Creation date check for Bio2RDF::Sgd took 0.49340057373046875s
Currency | Modification date check for Bio2RDF::Sgd took 0.5071287155151367s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 110.70835590362549s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 12.298948049545288s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.45631861686706543s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.27670764923095703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.25768375396728516s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.646102428436279s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8888833522796631s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6569831371307373s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.442108154296875s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.36001181602478s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.3723304271698s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.412184715270996s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.294968843460083s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.549381494522095s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7384660243988037s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4191431999206543s
Security | Sign check for Bio2RDF::Sgd took 0.2587895393371582s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 10.576516389846802s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.644707202911377s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010585784912109375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 13.910774230957031s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-sgd took 1046.1100599765778s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 9.393692016601562e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.296189546585083s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.021445751190185547s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.62396240234375e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.991900682449341s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.4881112575531006s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0005452632904052734s
Extra | Recovery of all triples for Bio2RDF::Sider took 19.07620358467102s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2221300601959229s
Amount of data | Number of triples check for Bio2RDF::Sider took 45.92119383811951s
Interoperability | New terms check for Bio2RDF::Sider took 42.469935178756714s
Versatility | Languages check for Bio2RDF::Sider took 60.245492935180664s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.30575108528137207s
Security | Check HTTPS for Bio2RDF::Sider took 0.1558082103729248s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.766345739364624s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3036618232727051s
Availability | RDF dump link check for Bio2RDF::Sider took 2.09922194480896s
License | MR license check for Bio2RDF::Sider took 0.5267848968505859s
License | HR license check for Bio2RDF::Sider took 60.254252433776855s
Amount of data | Number of property check for Bio2RDF::Sider took 0.2402791976928711s
Understandability | Number of label check for Bio2RDF::Sider took 9.551074266433716s
Understandability | URI regex check for Bio2RDF::Sider took 0.5978960990905762s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2702348232269287s
Verifiability | Authors check for Bio2RDF::Sider took 0.26998472213745117s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2696664333343506s
Performance | Throughput check for Bio2RDF::Sider took 11.1910560131073s
Amount of data | Check the number of entities for Bio2RDF::Sider took 76.66881036758423s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.5636787414550781s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3265659809112549s
Interlinking | skos check for Bio2RDF::Sider took 0.9817938804626465s
Interlinking | skos check for Bio2RDF::Sider took 0.4070241451263428s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.27240467071533203s
Currency | Creation date check for Bio2RDF::Sider took 0.5205826759338379s
Currency | Modification date check for Bio2RDF::Sider took 0.526771068572998s
Rep.Conc. | URIs length for Bio2RDF::Sider took 112.1516981124878s
Interoperability | New vocabularies check for Bio2RDF::Sider took 12.516298294067383s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.44928455352783203s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.279033899307251s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2744886875152588s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.9711244106292725s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.882868766784668s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6615886688232422s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.40523505210876465s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.27450752258301s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.4225447177886963s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.417629957199097s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3086881637573242s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.54703187942505s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7307021617889404s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4266057014465332s
Security | Sign check for Bio2RDF::Sider took 0.27396178245544434s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 11.052066087722778s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.4171743392944336s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 12.237658977508545s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-sider took 1048.9022154808044s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 9.298324584960938e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.31954073905944824s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.982948303222656e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-taxon took 3.043102741241455s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.47504711151123047s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006768703460693359s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 20.394622087478638s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2558231353759766s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 46.133203744888306s
Interoperability | New terms check for Bio2RDF::Taxonomy took 42.73026204109192s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.23894810676575s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2923886775970459s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.14837431907653809s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.5028693675994873s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3257269859313965s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.430037021636963s
License | MR license check for Bio2RDF::Taxonomy took 0.6325428485870361s
License | HR license check for Bio2RDF::Taxonomy took 60.24801278114319s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2668302059173584s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.149397373199463s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6016621589660645s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2660953998565674s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.25200629234313965s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2415003776550293s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.59266972541809s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 77.6979112625122s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.5816113948822021s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.338043212890625s
Interlinking | skos check for Bio2RDF::Taxonomy took 1.131399393081665s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.34581947326660156s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2573838233947754s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.4891834259033203s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5478956699371338s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 110.60578417778015s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 13.15844178199768s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4784376621246338s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2690143585205078s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.27280306816101074s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.969567775726318s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8864061832427979s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6703879833221436s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.4321584701538086s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 64.99431252479553s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.3795876502990723s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.244983196258545s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.2620453834533691s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.476654291152954s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7184724807739258s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.4381420612335205s
Security | Sign check for Bio2RDF::Taxonomy took 0.2715489864349365s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.387406826019287s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.49903178215026855s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00011396408081054688s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 12.175305128097534s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1048.9342863559723s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.14259123802185059s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.28338170051574707s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.021906614303588867s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 2.765655517578125e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 16.430092096328735s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4619722366333008s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0003943443298339844s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 20.45783019065857s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2402780055999756s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.30657696723938s
Interoperability | New terms check for Bio2RDF::Wormbase took 43.210493087768555s
Versatility | Languages check for Bio2RDF::Wormbase took 60.283873319625854s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2528696060180664s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.14425158500671387s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.7067646980285645s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3240981101989746s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.206676959991455s
License | MR license check for Bio2RDF::Wormbase took 0.5101890563964844s
License | HR license check for Bio2RDF::Wormbase took 60.258026361465454s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2592787742614746s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.088562250137329s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6014285087585449s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2676267623901367s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2800757884979248s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.2617838382720947s
Performance | Throughput check for Bio2RDF::Wormbase took 11.26426100730896s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 77.00074291229248s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.5847408771514893s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.34204626083374023s
Interlinking | skos check for Bio2RDF::Wormbase took 0.695620059967041s
Interlinking | skos check for Bio2RDF::Wormbase took 0.3576021194458008s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2705099582672119s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5079872608184814s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5201740264892578s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 109.67857098579407s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 12.781443119049072s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.41887354850769043s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.27497410774230957s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2666206359863281s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 7.511953592300415s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8912181854248047s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6572144031524658s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.40300846099853516s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.2433340549469s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.386059284210205s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.522532939910889s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.2969672679901123s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.54830193519592s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7267086505889893s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4149801731109619s
Security | Sign check for Bio2RDF::Wormbase took 0.28675270080566406s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 9.931649208068848s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.5382246971130371s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.987022399902344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 12.707362174987793s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1048.6112303733826s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.506111145019531e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.29091644287109375s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020207881927490234s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0006947517395019531s
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 8.344650268554688e-06s
INFO | --- Analysis for biografiasyvidas took 2.698230504989624s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.6155383586883545s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.2848317623138428s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0009694099426269531s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 9.083747863769531e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 4.76837158203125e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.280749559402466s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 9.274482727050781e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.30621957778930664s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.00543212890625e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.239776611328125e-05s
INFO | --- Analysis for biolod-pdb took 7.629490852355957s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6564030647277832s
Availability | VoID file availability check for BioModels RDF took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.32106590270996094s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.814697265625e-05s
Believability | Calculation of trust value for BioModels RDF took 1.2636184692382812e-05s
INFO | --- Analysis for biomodels-rdf took 4.104261159896851s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.1292495727539062s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2778606414794922s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.022388696670532227s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.956390380859375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1920928955078125e-05s
INFO | --- Analysis for Biop took 6.1488072872161865s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.083747863769531e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.292863130569458s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021371841430664062s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.838539123535156e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1682510375976562e-05s
INFO | --- Analysis for Bioportal took 2.7762670516967773s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 9.036064147949219e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2872614860534668s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.021062374114990234s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006864070892333984s
Believability | Calculation of trust value for Amphibian gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-aao took 3.2304370403289795s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.363059997558594e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2653224468231201s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.022066831588745117s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0003001689910888672s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-aba took 3.0343170166015625s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 9.703636169433594e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.3001422882080078s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.021668195724487305s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.001500844955444336s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-acgt took 3.1254966259002686s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.4345855712890625e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.304703950881958s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00035881996154785156s
Believability | Calculation of trust value for Animal natural history and life history took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-adw took 2.9577603340148926s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.29010438919067383s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02145671844482422s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004534721374511719s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-aeo took 2.976797103881836s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 9.1552734375e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2868020534515381s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009627342224121094s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-aero took 3.122534990310669s
Availability | SPARQL endpoint availability check for AI/RHEUM took 0.00011801719665527344s
Availability | VoID file availability check for AI/RHEUM took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.3159611225128174s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.0209503173828125s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00039076805114746094s
Believability | Calculation of trust value for AI/RHEUM took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-air took 2.991940498352051s
Availability | SPARQL endpoint availability check for Amino Acid took 0.00013566017150878906s
Availability | VoID file availability check for Amino Acid took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.2987372875213623s
Reputation | Calculation of the PageRank for Amino Acid took 0.02150416374206543s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0010538101196289062s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0003345012664794922s
Believability | Calculation of trust value for Amino Acid took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.9974937438964844s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2865760326385498s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020925045013427734s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002853870391845703s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-apo took 2.92875075340271s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 9.465217590332031e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2841775417327881s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.021040678024291992s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00024175643920898438s
Believability | Calculation of trust value for African Traditional Medicine took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-atmo took 2.915940284729004s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 8.869171142578125e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2865433692932129s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02134871482849121s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0009865760803222656s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 0.00011801719665527344s
Believability | Calculation of trust value for Amphibian taxonomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ato took 3.0418224334716797s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 9.632110595703125e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2759079933166504s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.021064281463623047s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013000965118408203s
Believability | Calculation of trust value for BioAssay Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bao took 2.9696531295776367s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 0.00012826919555664062s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.30811309814453125s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020938873291015625s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00037860870361328125s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 3.0917770862579346s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.30736708641052246s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.021124601364135742s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003218650817871094s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bcgo took 5.3197996616363525s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.29177331924438477s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.00141143798828125s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bdo took 3.0339179039001465s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.31424522399902344s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.0207669734954834s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005004405975341797s
Believability | Calculation of trust value for Basic Formal Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bfo took 2.9763576984405518s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 8.988380432128906e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2963082790374756s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.021046161651611328s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007281303405761719s
Believability | Calculation of trust value for Bleeding History Phenotype took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bho took 3.016148328781128s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 9.34600830078125e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2859771251678467s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.021314620971679688s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0009481906890869141s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0005145072937011719s
Believability | Calculation of trust value for Bilateria anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bila took 3.010957956314087s
Availability | SPARQL endpoint availability check for BIRNLex took 0.00012803077697753906s
Availability | VoID file availability check for BIRNLex took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.3160076141357422s
Reputation | Calculation of the PageRank for BIRNLex took 0.02148270606994629s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014557838439941406s
Believability | Calculation of trust value for BIRNLex took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-birnlex took 2.9523696899414062s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.29797887802124023s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007283687591552734s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bootstrep took 3.0609354972839355s
Availability | SPARQL endpoint availability check for BioPAX took 4.315376281738281e-05s
Availability | VoID file availability check for BioPAX took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for BioPAX took 0.3357353210449219s
Reputation | Calculation of the PageRank for BioPAX took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.632110595703125e-05s
Believability | Calculation of trust value for BioPAX took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bp took 3.0782065391540527s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 0.00014925003051757812s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2869863510131836s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02101588249206543s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003285408020019531s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 3.033308744430542s
Availability | SPARQL endpoint availability check for Spatial Ontology took 9.870529174804688e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.3150520324707031s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.021154403686523438s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00020575523376464844s
Believability | Calculation of trust value for Spatial Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bspo took 3.0600507259368896s
Availability | SPARQL endpoint availability check for BioTop took 4.482269287109375e-05s
Availability | VoID file availability check for BioTop took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for BioTop took 0.2746143341064453s
Reputation | Calculation of the PageRank for BioTop took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006475448608398438s
Believability | Calculation of trust value for BioTop took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bt took 2.9529123306274414s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.4345855712890625e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.26378321647644043s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.0208282470703125s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008730888366699219s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bto took 2.972979784011841s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3380131721496582s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02231287956237793s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018329620361328125s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-canco took 3.400696277618408s
Availability | SPARQL endpoint availability check for CAO took 4.363059997558594e-05s
Availability | VoID file availability check for CAO took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for CAO took 0.3387923240661621s
Reputation | Calculation of the PageRank for CAO took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for CAO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005872249603271484s
Believability | Calculation of trust value for CAO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cao took 2.995255947113037s
Availability | SPARQL endpoint availability check for CareLex took 9.083747863769531e-05s
Availability | VoID file availability check for CareLex took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for CareLex took 0.2863945960998535s
Reputation | Calculation of the PageRank for CareLex took 0.02089834213256836s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.125999450683594e-05s
Believability | Calculation of trust value for CareLex took 7.62939453125e-06s
INFO | --- Analysis for bioportal-carelex took 2.9218883514404297s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.27272486686706543s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008087158203125s
Believability | Calculation of trust value for Cell Cycle Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-cco took 2.9220473766326904s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.3255641460418701s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.022234439849853516s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025844573974609375s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-cdao took 2.969968318939209s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.553794860839844e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2852485179901123s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02243518829345703s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008001327514648438s
Believability | Calculation of trust value for Chemical entities of biological interest took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-chebi took 3.04526948928833s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 9.059906005859375e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.32445621490478516s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02128314971923828s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00027561187744140625s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.9460442066192627s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 9.560585021972656e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.30251383781433105s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.024324417114257812s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0011548995971679688s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0009300708770751953s
Believability | Calculation of trust value for Chemical Information Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cheminf took 3.004723310470581s
Availability | SPARQL endpoint availability check for Cell type took 9.179115295410156e-05s
Availability | VoID file availability check for Cell type took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Cell type took 0.32085299491882324s
Reputation | Calculation of the PageRank for Cell type took 0.02141594886779785s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003960132598876953s
Believability | Calculation of trust value for Cell type took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-cl took 2.9798426628112793s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.31464552879333496s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.021263837814331055s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008046627044677734s
Believability | Calculation of trust value for Cell Line Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-clo took 3.042304515838623s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.3393979072570801s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.023084163665771484s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017261505126953125s
Believability | Calculation of trust value for Clinical Measurement Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cmo took 3.077118158340454s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.27484917640686035s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020456314086914062s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-cno took 2.9300179481506348s
Availability | SPARQL endpoint availability check for Wheat trait took 4.673004150390625e-05s
Availability | VoID file availability check for Wheat trait took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.32451820373535156s
Reputation | Calculation of the PageRank for Wheat trait took 0.021510601043701172s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.507469177246094e-05s
Believability | Calculation of trust value for Wheat trait took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-co_wheat took 3.001953125s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 5.1975250244140625e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.305192232131958s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020977258682250977s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003376007080078125s
Believability | Calculation of trust value for Cognitive Atlas took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cogat took 3.0273749828338623s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.3033764362335205s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.021211862564086914s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007948875427246094s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cogpo took 2.9266889095306396s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 8.869171142578125e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.33463549613952637s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.021141767501831055s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00040721893310546875s
Believability | Calculation of trust value for Current Procedural Terminology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cpt took 2.9465630054473877s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.458427429199219e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3303954601287842s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020987749099731445s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017952919006347656s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 7.62939453125e-06s
INFO | --- Analysis for bioportal-csp took 3.373134136199951s
Availability | SPARQL endpoint availability check for COSTART took 9.083747863769531e-05s
Availability | VoID file availability check for COSTART took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for COSTART took 0.3257875442504883s
Reputation | Calculation of the PageRank for COSTART took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009605884552001953s
Believability | Calculation of trust value for COSTART took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cst took 2.95920991897583s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 9.036064147949219e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.00041365623474121094s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.3067333698272705s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.022049665451049805s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004940032958984375s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ctcae took 3.0199193954467773s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.649162292480469e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2884378433227539s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02087879180908203s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00044417381286621094s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ctx took 2.9891867637634277s
Availability | SPARQL endpoint availability check for Dendritic cell took 0.00018286705017089844s
Availability | VoID file availability check for Dendritic cell took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.3208765983581543s
Reputation | Calculation of the PageRank for Dendritic cell took 0.021576881408691406s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002903938293457031s
Believability | Calculation of trust value for Dendritic cell took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.9927761554718018s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.988380432128906e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2743265628814697s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020954370498657227s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.821487426757812e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ddanat took 2.9742021560668945s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.3269319534301758s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.021905183792114258s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009334087371826172s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ddi took 2.972790002822876s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.27263855934143066s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02297043800354004s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.487701416015625e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-diagnosticont took 2.981062650680542s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.3169422149658203s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.022403240203857422s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016164779663085938s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.9323949813842773s
Availability | SPARQL endpoint availability check for Human disease ontology took 9.226799011230469e-05s
Availability | VoID file availability check for Human disease ontology took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2899610996246338s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006330013275146484s
Believability | Calculation of trust value for Human disease ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-doid took 3.0115926265716553s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 5.245208740234375e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.27580952644348145s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008268356323242188s
Believability | Calculation of trust value for Electrocardiography Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ecg took 2.9802684783935547s
Availability | SPARQL endpoint availability check for Evidence codes took 0.00012683868408203125s
Availability | VoID file availability check for Evidence codes took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.33690357208251953s
Reputation | Calculation of the PageRank for Evidence codes took 0.022521495819091797s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.0517578125e-05s
Believability | Calculation of trust value for Evidence codes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-eco took 2.9696688652038574s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3387107849121094s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017695426940917969s
Believability | Calculation of trust value for Experimental Factor Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-efo took 3.3710734844207764s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 9.059906005859375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.29448580741882324s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011315345764160156s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ehda took 2.984593152999878s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 5.6743621826171875e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.3516833782196045s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02026844024658203s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007305145263671875s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.9815447330474854s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.315376281738281e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.30129027366638184s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.02086949348449707s
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.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005140304565429688s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.86311674118042s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 9.5367431640625e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.3013625144958496s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.0517578125e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-emap took 3.0747885704040527s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Environment Ontology took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.29688596725463867s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00038552284240722656s
Believability | Calculation of trust value for Environment Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-envo took 2.9496047496795654s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 8.869171142578125e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.3031299114227295s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0003261566162109375s
Believability | Calculation of trust value for Plant environmental conditions took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-eo took 2.916501045227051s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 0.00011229515075683594s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2831425666809082s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02113485336303711s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012080669403076172s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ep took 2.8816967010498047s
Availability | SPARQL endpoint availability check for Epilepsy took 4.410743713378906e-05s
Availability | VoID file availability check for Epilepsy took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.29909729957580566s
Reputation | Calculation of the PageRank for Epilepsy took 0.02105093002319336s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001251697540283203s
Believability | Calculation of trust value for Epilepsy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-epileponto took 2.8620805740356445s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 0.0001285076141357422s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.28555727005004883s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.02077960968017578s
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.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.00116729736328125s
Believability | Calculation of trust value for eagle-i research resource ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ero took 2.9371728897094727s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.649162292480469e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.3231487274169922s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.021326065063476562s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011942386627197266s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ev took 2.8843636512756348s
Availability | SPARQL endpoint availability check for ExO took 8.654594421386719e-05s
Availability | VoID file availability check for ExO took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for ExO took 0.2913017272949219s
Reputation | Calculation of the PageRank for ExO took 0.02237248420715332s
Interlinking | Calculation of Degree of Connection for ExO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00024008750915527344s
Believability | Calculation of trust value for ExO took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-exo took 2.944692611694336s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.458427429199219e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0010900497436523438s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.28436851501464844s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00010967254638671875s
Believability | Calculation of trust value for Fungal gross anatomy took 7.62939453125e-06s
INFO | --- Analysis for bioportal-fao took 2.896834373474121s
Availability | SPARQL endpoint availability check for Biological imaging methods took 5.745887756347656e-05s
Availability | VoID file availability check for Biological imaging methods took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2864806652069092s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0001876354217529297s
Believability | Calculation of trust value for Biological imaging methods took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fbbi took 2.91021728515625s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 0.00010466575622558594s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2764151096343994s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020803451538085938s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006380081176757812s
Believability | Calculation of trust value for Drosophila gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fbbt took 2.982642650604248s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.291534423828125e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.3074331283569336s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004184246063232422s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-fbcv took 3.0443480014801025s
Availability | SPARQL endpoint availability check for Drosophila development took 4.315376281738281e-05s
Availability | VoID file availability check for Drosophila development took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.3129744529724121s
Reputation | Calculation of the PageRank for Drosophila development took 0.022507905960083008s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.410743713378906e-05s
Believability | Calculation of trust value for Drosophila development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fbdv took 2.8957102298736572s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.916854858398438e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.3235504627227783s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02147650718688965s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003745555877685547s
Believability | Calculation of trust value for Fly taxonomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-fbsp took 3.09425687789917s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.2438507080078125e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2833409309387207s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022339820861816406s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.983126640319824s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 7.939338684082031e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2767319679260254s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.022480249404907227s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0009970664978027344s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.000499725341796875s
Believability | Calculation of trust value for Family Health History Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fhho took 2.992111921310425s
Availability | SPARQL endpoint availability check for Influenza Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.2967231273651123s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0011610984802246094s
Believability | Calculation of trust value for Influenza Ontology took 1.7881393432617188e-05s
INFO | --- Analysis for bioportal-flu took 2.869176149368286s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 9.226799011230469e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.28408384323120117s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.021140098571777344s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.246566772460938e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fma took 3.026859760284424s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.29252123832702637s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00013017654418945312s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fypo took 2.9116370677948s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.29407167434692383s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0009074211120605469s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.00010967254638671875s
Believability | Calculation of trust value for GeoSpecies Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-geospecies took 2.877575159072876s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2854750156402588s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016021728515625s
Believability | Calculation of trust value for General Formal Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-gfo took 2.9217159748077393s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.482269287109375e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.3050529956817627s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.0214083194732666s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.000957489013671875s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0009710788726806641s
Believability | Calculation of trust value for General Formal Ontology: Biology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-gfo-bio took 3.061629295349121s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.315376281738281e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.28656840324401855s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.021047353744506836s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.000835418701171875s
Believability | Calculation of trust value for Gene Ontology Extension took 7.62939453125e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.9716105461120605s
Availability | SPARQL endpoint availability check for Gene Ontology took 9.5367431640625e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.3041718006134033s
Reputation | Calculation of the PageRank for Gene Ontology took 0.022518157958984375s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008571147918701172s
Believability | Calculation of trust value for Gene Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-go_x2 took 3.028841972351074s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 0.00010991096496582031s
Availability | VoID file availability check for Cereal Plant Development took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.27962255477905273s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02080988883972168s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.457069396972656e-05s
Believability | Calculation of trust value for Cereal Plant Development took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-gro took 3.2985012531280518s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 8.726119995117188e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.3397040367126465s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00041985511779785156s
Believability | Calculation of trust value for Cereal plant gross anatomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-gro_x1 took 3.0903987884521484s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.29497218132019043s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007321834564208984s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.974543571472168s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2744872570037842s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005452632904052734s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-hao took 2.8723385334014893s
Availability | SPARQL endpoint availability check for HCPCS took 9.560585021972656e-05s
Availability | VoID file availability check for HCPCS took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for HCPCS took 0.3237175941467285s
Reputation | Calculation of the PageRank for HCPCS took 0.022571325302124023s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002281665802001953s
Believability | Calculation of trust value for HCPCS took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-hcpcs took 3.0314064025878906s
Availability | SPARQL endpoint availability check for Health Level Seven took 9.560585021972656e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.28984498977661133s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02133655548095703s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0013115406036376953s
Believability | Calculation of trust value for Health Level Seven took 7.62939453125e-06s
INFO | --- Analysis for bioportal-hl7 took 3.0120489597320557s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 9.036064147949219e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.32836246490478516s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.021445035934448242s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003407001495361328s
Believability | Calculation of trust value for HEALTH_INDICATORS took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.9630134105682373s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 5.14984130859375e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.27825021743774414s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.022205591201782227s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.7670135498046875e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-hom took 2.8677895069122314s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.57763671875e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.31032872200012207s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.021692276000976562s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.4332275390625e-05s
Believability | Calculation of trust value for HOM-HARVARD took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hom_harvard took 3.081942558288574s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.2971973419189453s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006804466247558594s
Believability | Calculation of trust value for Human Phenotype Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.9450488090515137s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 5.8650970458984375e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.26477932929992676s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02119588851928711s
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.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010225772857666016s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-hpio took 3.010017156600952s
Availability | SPARQL endpoint availability check for HUGO took 0.00014472007751464844s
Availability | VoID file availability check for HUGO took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for HUGO took 0.3083460330963135s
Reputation | Calculation of the PageRank for HUGO took 0.02260899543762207s
Interlinking | Calculation of Degree of Connection for HUGO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.82012939453125e-05s
Believability | Calculation of trust value for HUGO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hugo took 2.969285488128662s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.2877635955810547s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.022364377975463867s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006575584411621094s
Believability | Calculation of trust value for Information Artifact Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-iao took 2.9495389461517334s
Availability | SPARQL endpoint availability check for ICD10 took 4.291534423828125e-05s
Availability | VoID file availability check for ICD10 took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for ICD10 took 0.3392751216888428s
Reputation | Calculation of the PageRank for ICD10 took 0.022234201431274414s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008101463317871094s
Believability | Calculation of trust value for ICD10 took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-icd10 took 3.010200262069702s
Availability | SPARQL endpoint availability check for ICD10CM took 9.131431579589844e-05s
Availability | VoID file availability check for ICD10CM took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.2749350070953369s
Reputation | Calculation of the PageRank for ICD10CM took 0.02213144302368164s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006597042083740234s
Believability | Calculation of trust value for ICD10CM took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-icd10cm took 3.031765937805176s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.363059997558594e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.2743525505065918s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.021413326263427734s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.000171661376953125s
Believability | Calculation of trust value for ICD-10-PCS took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.9730217456817627s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.38690185546875e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.3260781764984131s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006723403930664062s
Believability | Calculation of trust value for International Classification of Diseases took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.9972434043884277s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0013747215270996094s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2964143753051758s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.022764205932617188s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004391670227050781s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 1.8358230590820312e-05s
INFO | --- Analysis for bioportal-icf_x1 took 2.9880049228668213s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 8.797645568847656e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.31970858573913574s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012273788452148438s
Believability | Calculation of trust value for International Classification for Nursing Practice took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icnp took 3.038025140762329s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 9.369850158691406e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2683126926422119s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.021102190017700195s
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.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004572868347167969s
Believability | Calculation of trust value for International Classification of Primary Care took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icpc took 2.8483083248138428s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.3392181396484375e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.30045413970947266s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008540153503417969s
Believability | Calculation of trust value for ICPC-2 PLUS took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.885193109512329s
Availability | SPARQL endpoint availability check for ICPS Network took 4.363059997558594e-05s
Availability | VoID file availability check for ICPS Network took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2740511894226074s
Reputation | Calculation of the PageRank for ICPS Network took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00021505355834960938s
Believability | Calculation of trust value for ICPS Network took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icps took 2.9516608715057373s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.33483147621154785s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008530616760253906s
Believability | Calculation of trust value for Infectious Disease Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ido took 3.111098527908325s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 0.00020933151245117188s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.28705906867980957s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02089381217956543s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011374950408935547s
Believability | Calculation of trust value for Brucellosis Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-idobru took 2.9932219982147217s
Availability | SPARQL endpoint availability check for Malaria Ontology took 9.989738464355469e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.29700279235839844s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.02084493637084961s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012993812561035156s
Believability | Calculation of trust value for Malaria Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-idomal took 3.0090291500091553s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.410743713378906e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.28313279151916504s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0002989768981933594s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-iev took 3.040038585662842s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 9.584426879882812e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2877953052520752s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.0001595020294189453s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-imgt took 2.947932720184326s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.3392181396484375e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2857518196105957s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.021157264709472656s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005133152008056641s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-imr took 3.048231363296509s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.28926873207092285s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007765293121337891s
Believability | Calculation of trust value for Interaction Network Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ino took 2.9557008743286133s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 9.441375732421875e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.29833507537841797s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.022333621978759766s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0009267330169677734s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.504753112792969e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.970905065536499s
Availability | SPARQL endpoint availability check for IxnO took 9.34600830078125e-05s
Availability | VoID file availability check for IxnO took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for IxnO took 0.28672122955322266s
Reputation | Calculation of the PageRank for IxnO took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0001983642578125s
Believability | Calculation of trust value for IxnO took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ixno took 2.9837045669555664s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.38690185546875e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.3160700798034668s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.021541357040405273s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00042700767517089844s
Believability | Calculation of trust value for SysMO-JERM took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-jerm took 3.006513833999634s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 8.082389831542969e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.254352331161499s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-kisao took 2.8810629844665527s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 0.0005645751953125s
Availability | VoID file availability check for Loggerhead nesting took 0.0003695487976074219s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.29719090461730957s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0001976490020751953s
Believability | Calculation of trust value for Loggerhead nesting took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-lhn took 3.0703985691070557s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.32373619079589844s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020813941955566406s
Believability | Calculation of trust value for Lipid Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-lipro took 2.9728786945343018s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 0.0001087188720703125s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.33336520195007324s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0017933845520019531s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-lnc took 3.272714138031006s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.3170657157897949s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006473064422607422s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ma took 2.9509596824645996s
Availability | SPARQL endpoint availability check for Multiple alignment took 7.867813110351562e-05s
Availability | VoID file availability check for Multiple alignment took 0.0003974437713623047s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.27265143394470215s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020932912826538086s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0008969306945800781s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00023436546325683594s
Believability | Calculation of trust value for Multiple alignment took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mao took 2.8758931159973145s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 5.459785461425781e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2620217800140381s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006835460662841797s
Believability | Calculation of trust value for Minimal anatomical terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mat took 2.8805599212646484s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 9.107589721679688e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2646167278289795s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004253387451171875s
Believability | Calculation of trust value for Breast tissue cell lines took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.9188590049743652s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2956430912017822s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007421970367431641s
Believability | Calculation of trust value for Cell line ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mccl took 2.8582472801208496s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cell line ontology took 0.00040721893310546875s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.3542182445526123s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021480083465576172s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0013766288757324219s
Believability | Calculation of trust value for Cell line ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.9318199157714844s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 8.749961853027344e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.30565309524536133s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00023984909057617188s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mcv took 2.9987685680389404s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 9.608268737792969e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.27965712547302246s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.021763086318969727s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017690658569335938s
Believability | Calculation of trust value for Master Drug Data Base took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mddb took 2.971184015274048s
Availability | SPARQL endpoint availability check for MedDRA took 9.036064147949219e-05s
Availability | VoID file availability check for MedDRA took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for MedDRA took 0.28873491287231445s
Reputation | Calculation of the PageRank for MedDRA took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011396408081054688s
Believability | Calculation of trust value for MedDRA took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mdr took 2.809931755065918s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.267692565917969e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.27703213691711426s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008854866027832031s
Believability | Calculation of trust value for MedlinePlus Health Topics took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.8016982078552246s
Availability | SPARQL endpoint availability check for MeGO took 4.315376281738281e-05s
Availability | VoID file availability check for MeGO took 0.00033092498779296875s
Completeness | Calculation of interlinking completeness for MeGO took 0.27132081985473633s
Reputation | Calculation of the PageRank for MeGO took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014662742614746094s
Believability | Calculation of trust value for MeGO took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mego took 2.7788732051849365s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.363059997558594e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.34850621223449707s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0017993450164794922s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.369540214538574s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.30701231956481934s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.02184462547302246s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006411075592041016s
Believability | Calculation of trust value for Mental Functioning Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mf took 2.956511974334717s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.4345855712890625e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.00039768218994140625s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.31174683570861816s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005707740783691406s
Believability | Calculation of trust value for Medaka fish anatomy and development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mfo took 2.9508960247039795s
Availability | SPARQL endpoint availability check for Emotion Ontology took 9.322166442871094e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.3355717658996582s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007541179656982422s
Believability | Calculation of trust value for Emotion Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mfoem took 2.9662818908691406s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.27805304527282715s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02220296859741211s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010514259338378906s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mhc took 2.885256052017212s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 8.7738037109375e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2743957042694092s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006732940673828125s
Believability | Calculation of trust value for Protein-protein interaction took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mi took 3.2141926288604736s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 9.036064147949219e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.28165411949157715s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007112026214599609s
Believability | Calculation of trust value for Mosquito insecticide resistance took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-miro took 3.351992607116699s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 0.0005791187286376953s
Availability | VoID file availability check for Measurement Method Ontology took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.27825474739074707s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013208389282226562s
Believability | Calculation of trust value for Measurement Method Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mmo took 3.001899242401123s
Availability | SPARQL endpoint availability check for MGED Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for MGED Ontology took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.3098132610321045s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00039267539978027344s
Believability | Calculation of trust value for MGED Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mo took 3.0112767219543457s
Availability | SPARQL endpoint availability check for Protein modification took 9.107589721679688e-05s
Availability | VoID file availability check for Protein modification took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2621629238128662s
Reputation | Calculation of the PageRank for Protein modification took 0.02214956283569336s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021982192993164062s
Believability | Calculation of trust value for Protein modification took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mod took 2.9659769535064697s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 5.1021575927734375e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.29123878479003906s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006518363952636719s
Believability | Calculation of trust value for Mammalian phenotype took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mp took 3.0084197521209717s
Availability | SPARQL endpoint availability check for Mouse pathology took 9.751319885253906e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.28821611404418945s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004792213439941406s
Believability | Calculation of trust value for Mouse pathology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mpath took 3.1696815490722656s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.315376281738281e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.28645896911621094s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.021045923233032227s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00035858154296875s
Believability | Calculation of trust value for Mass spectrometry took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ms took 2.9911949634552s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.315376281738281e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.37096691131591797s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0008456707000732422s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.001961946487426758s
Believability | Calculation of trust value for Medical Subject Headings took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-msh took 3.4227054119110107s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 5.507469177246094e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.3283240795135498s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.021872997283935547s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017404556274414062s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mthch took 2.951869249343872s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0009565353393554688s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.29670143127441406s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007853507995605469s
Believability | Calculation of trust value for Natural Products Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-natpro took 2.9552626609802246s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 8.821487426757812e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.3338944911956787s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007889270782470703s
Believability | Calculation of trust value for NCBI organismal classification took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.997506856918335s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.96453857421875e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3725011348724365s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.021786928176879883s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002021312713623047s
Believability | Calculation of trust value for NCI Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ncit took 3.451157808303833s
Availability | SPARQL endpoint availability check for National Drug Data File took 8.726119995117188e-05s
Availability | VoID file availability check for National Drug Data File took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.31539225578308105s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006132125854492188s
Believability | Calculation of trust value for National Drug Data File took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nddf took 3.0180435180664062s
Availability | SPARQL endpoint availability check for National Drug File took 9.274482727050781e-05s
Availability | VoID file availability check for National Drug File took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for National Drug File took 0.3386390209197998s
Reputation | Calculation of the PageRank for National Drug File took 0.021295785903930664s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012087821960449219s
Believability | Calculation of trust value for National Drug File took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ndfrt took 3.0174901485443115s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 8.940696716308594e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.27833127975463867s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011475086212158203s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 3.056554079055786s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.29065775871276855s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006594657897949219s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-neomark took 2.8701326847076416s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.28696298599243164s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.022249221801757812s
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.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00011968612670898438s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 3.0835561752319336s
Availability | SPARQL endpoint availability check for NIFSTD took 4.5299530029296875e-05s
Availability | VoID file availability check for NIFSTD took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3666062355041504s
Reputation | Calculation of the PageRank for NIFSTD took 0.022104740142822266s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019450187683105469s
Believability | Calculation of trust value for NIFSTD took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nif took 3.492375135421753s
Availability | SPARQL endpoint availability check for NIF Cell took 9.965896606445312e-05s
Availability | VoID file availability check for NIF Cell took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.30372118949890137s
Reputation | Calculation of the PageRank for NIF Cell took 0.02247309684753418s
Interlinking | Calculation of Degree of Connection for NIF Cell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013341903686523438s
Believability | Calculation of trust value for NIF Cell took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.991142749786377s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 8.893013000488281e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.29859089851379395s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.02098250389099121s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013740062713623047s
Believability | Calculation of trust value for NIF Dysfunction took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.9416825771331787s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.31289076805114746s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005435943603515625s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nigo took 4.107787370681763s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 9.250640869140625e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.28345227241516113s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.021533489227294922s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005528926849365234s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-nmr took 3.00022554397583s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.3263881206512451s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.0208742618560791s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011038780212402344s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nonrctontology took 3.046834945678711s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2856016159057617s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020984888076782227s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011758804321289062s
Believability | Calculation of trust value for NanoParticle Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-npo took 2.9643802642822266s
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.0004630088806152344s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2779960632324219s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007677078247070312s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 7.62939453125e-06s
INFO | --- Analysis for bioportal-oae took 3.0277137756347656s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 9.274482727050781e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.3003652095794678s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014362335205078125s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-obi took 2.9668569564819336s
Availability | SPARQL endpoint availability check for OBOE took 4.291534423828125e-05s
Availability | VoID file availability check for OBOE took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for OBOE took 0.3357810974121094s
Reputation | Calculation of the PageRank for OBOE took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010943412780761719s
Believability | Calculation of trust value for OBOE took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-oboe took 2.866954803466797s
Availability | SPARQL endpoint availability check for OBOE SBC took 8.726119995117188e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.28154706954956055s
Reputation | Calculation of the PageRank for OBOE SBC took 0.021739482879638672s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007989406585693359s
Believability | Calculation of trust value for OBOE SBC took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.8370275497436523s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 0.00011849403381347656s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.30396485328674316s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005795955657958984s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ocre took 2.9235546588897705s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 9.036064147949219e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.30109333992004395s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008571147918701172s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-odgi took 2.906646728515625s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 9.274482727050781e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.27155351638793945s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020883798599243164s
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.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0009508132934570312s
Believability | Calculation of trust value for Ontology for Genetic Interval took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ogi took 2.9200336933135986s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 0.00010824203491210938s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.3069627285003662s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02109074592590332s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00029349327087402344s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ogmd took 3.0015265941619873s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 8.893013000488281e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.3051481246948242s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006890296936035156s
Believability | Calculation of trust value for Ontology for General Medical Science took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ogms took 2.923255205154419s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.315376281738281e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0011715888977050781s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.29204368591308594s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.001119852066040039s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-omim took 2.98903751373291s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 5.14984130859375e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.3267326354980469s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.022314786911010742s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003592967987060547s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-omit took 3.0215306282043457s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.30068421363830566s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02213287353515625s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.000598907470703125s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-omrse took 2.678070068359375s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 9.250640869140625e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.3366987705230713s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0008039474487304688s
Believability | Calculation of trust value for Ontology of Data Mining took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ontodm took 3.1079323291778564s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 0.00014138221740722656s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.3015313148498535s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002560615539550781s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ontodt took 2.954423427581787s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 0.0001621246337890625s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.30420541763305664s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0005984306335449219s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.931032657623291s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 9.107589721679688e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.28847789764404297s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009593963623046875s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-opl took 3.0161099433898926s
Availability | SPARQL endpoint availability check for Phenotypic quality took 8.893013000488281e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.3177783489227295s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008752346038818359s
Believability | Calculation of trust value for Phenotypic quality took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-pato took 3.013932228088379s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.315376281738281e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.30627989768981934s
Reputation | Calculation of the PageRank for Physician Data Query took 0.0218813419342041s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008165836334228516s
Believability | Calculation of trust value for Physician Data Query took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pdq took 2.8408985137939453s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.4345855712890625e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.31375598907470703s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007870197296142578s
Believability | Calculation of trust value for Pediatric Terminology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pedterm took 2.9044978618621826s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.3258962631225586s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.022235393524169922s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0001926422119140625s
Believability | Calculation of trust value for Parasite Experiment Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-peo took 2.8977339267730713s
Availability | SPARQL endpoint availability check for PHARE took 9.775161743164062e-05s
Availability | VoID file availability check for PHARE took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for PHARE took 0.29334282875061035s
Reputation | Calculation of the PageRank for PHARE took 0.021048784255981445s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006301403045654297s
Believability | Calculation of trust value for PHARE took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-phare took 2.9400360584259033s
Availability | SPARQL endpoint availability check for PKO_Re took 9.250640869140625e-05s
Availability | VoID file availability check for PKO_Re took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.27660322189331055s
Reputation | Calculation of the PageRank for PKO_Re took 0.0207064151763916s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00017404556274414062s
Believability | Calculation of trust value for PKO_Re took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-pko took 2.7875161170959473s
Availability | SPARQL endpoint availability check for PMA 2010 took 8.869171142578125e-05s
Availability | VoID file availability check for PMA 2010 took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.306138277053833s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008769035339355469s
Believability | Calculation of trust value for PMA 2010 took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pma took 2.9513213634490967s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 8.96453857421875e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.3057105541229248s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001766681671142578s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pmr took 2.9736948013305664s
Availability | SPARQL endpoint availability check for Plant Anatomy took 9.083747863769531e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2951645851135254s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00038504600524902344s
Believability | Calculation of trust value for Plant Anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-po took 2.8557236194610596s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 9.036064147949219e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.27910399436950684s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.022311925888061523s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.556510925292969e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.910482883453369s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.887580871582031e-05s
Availability | VoID file availability check for Plant Ontology took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.3171689510345459s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004379749298095703s
Believability | Calculation of trust value for Plant Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.882157564163208s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 9.012222290039062e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.28103113174438477s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.0208587646484375s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006530284881591797s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pr took 2.992018222808838s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 9.369850158691406e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2877950668334961s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00026035308837890625s
Believability | Calculation of trust value for Proteomics data and process provenance took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-propreo took 2.9152379035949707s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.295363187789917s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012803077697753906s
Believability | Calculation of trust value for Pathway ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pw took 2.863150119781494s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 9.226799011230469e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.30802345275878906s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-qibo took 2.9126410484313965s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 9.107589721679688e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.37479138374328613s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.022516727447509766s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0018305778503417969s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rcd took 3.4874510765075684s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 0.00011920928955078125s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.27442049980163574s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020947933197021484s
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.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001327991485595703s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-rctontology took 2.957278251647949s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.000396728515625s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2857801914215088s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.022716760635375977s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.632110595703125e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-repo took 3.056173324584961s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.673004150390625e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.32375454902648926s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02269744873046875s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0002009868621826172s
Believability | Calculation of trust value for Physico-chemical process took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rex took 2.944110870361328s
Availability | SPARQL endpoint availability check for RadLex took 9.298324584960938e-05s
Availability | VoID file availability check for RadLex took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for RadLex took 0.28921031951904297s
Reputation | Calculation of the PageRank for RadLex took 0.021092653274536133s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0014913082122802734s
Believability | Calculation of trust value for RadLex took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rid took 3.020829439163208s
Availability | SPARQL endpoint availability check for RNA ontology took 5.245208740234375e-05s
Availability | VoID file availability check for RNA ontology took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2758612632751465s
Reputation | Calculation of the PageRank for RNA ontology took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005767345428466797s
Believability | Calculation of trust value for RNA ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rnao took 2.8987550735473633s
Availability | SPARQL endpoint availability check for Role Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Role Ontology took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.30234217643737793s
Reputation | Calculation of the PageRank for Role Ontology took 0.021180391311645508s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018835067749023438s
Believability | Calculation of trust value for Role Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-roleo took 2.9386520385742188s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.32613277435302734s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02114105224609375s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00017833709716796875s
Believability | Calculation of trust value for Rat Strain Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rs took 3.0036678314208984s
Availability | SPARQL endpoint availability check for RxNORM took 4.673004150390625e-05s
Availability | VoID file availability check for RxNORM took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for RxNORM took 0.28452539443969727s
Reputation | Calculation of the PageRank for RxNORM took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006654262542724609s
Believability | Calculation of trust value for RxNORM took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.9939918518066406s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 9.250640869140625e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.28847503662109375s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010228157043457031s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sao took 3.036939859390259s
Availability | SPARQL endpoint availability check for Systems Biology took 9.083747863769531e-05s
Availability | VoID file availability check for Systems Biology took 0.001058340072631836s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2990138530731201s
Reputation | Calculation of the PageRank for Systems Biology took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00045490264892578125s
Believability | Calculation of trust value for Systems Biology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-sbo took 2.8297829627990723s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0003998279571533203s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.3139162063598633s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02075362205505371s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010061264038085938s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sbro took 3.0530364513397217s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.3382127285003662s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02122211456298828s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013332366943359375s
Believability | Calculation of trust value for Sleep Domain Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sdo took 2.9550464153289795s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.5299530029296875e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.30672192573547363s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003352165222167969s
Believability | Calculation of trust value for Sample processing and separation techniques took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-sep took 2.980168342590332s
Availability | SPARQL endpoint availability check for Student Health Record took 9.322166442871094e-05s
Availability | VoID file availability check for Student Health Record took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2916386127471924s
Reputation | Calculation of the PageRank for Student Health Record took 0.02274799346923828s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.00045871734619140625s
Believability | Calculation of trust value for Student Health Record took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-shr took 2.973132610321045s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007500648498535156s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.3083505630493164s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012297630310058594s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sio took 3.692448377609253s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.649162292480469e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.3137474060058594s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00021529197692871094s
Believability | Calculation of trust value for Situation-Based Access Control took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sitbac took 2.9727113246917725s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 9.179115295410156e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3418610095977783s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.022806167602539062s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019042491912841797s
Believability | Calculation of trust value for SNOMED Clinical Terms took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-snomedct took 3.426774501800537s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.28666067123413086s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007145404815673828s
Believability | Calculation of trust value for SNP-Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-snpo took 3.075295925140381s
Availability | SPARQL endpoint availability check for Sequence types and features took 8.869171142578125e-05s
Availability | VoID file availability check for Sequence types and features took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2892923355102539s
Reputation | Calculation of the PageRank for Sequence types and features took 0.021539688110351562s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005660057067871094s
Believability | Calculation of trust value for Sequence types and features took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.875546932220459s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 9.012222290039062e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.33260440826416016s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.021187543869018555s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0016026496887207031s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sopharm took 3.334188461303711s
Availability | SPARQL endpoint availability check for SoyOntology took 8.749961853027344e-05s
Availability | VoID file availability check for SoyOntology took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.30712080001831055s
Reputation | Calculation of the PageRank for SoyOntology took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.000125885009765625s
Believability | Calculation of trust value for SoyOntology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-soy took 2.9550421237945557s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for Spider Ontology took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2925281524658203s
Reputation | Calculation of the PageRank for Spider Ontology took 0.022091150283813477s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00031447410583496094s
Believability | Calculation of trust value for Spider Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-spd took 2.928826332092285s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.30440354347229004s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.02190375328063965s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002739429473876953s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-spto took 2.9386343955993652s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2772979736328125s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02118992805480957s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004374980926513672s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sso took 2.94970703125s
Availability | SPARQL endpoint availability check for Software Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Software Ontology took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2766449451446533s
Reputation | Calculation of the PageRank for Software Ontology took 0.021775007247924805s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00040078163146972656s
Believability | Calculation of trust value for Software Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-swo took 2.905608654022217s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.28573107719421387s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.021927356719970703s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00024199485778808594s
Believability | Calculation of trust value for Tick gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-tads took 2.8786044120788574s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.30469179153442383s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008831024169921875s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tao took 2.9847941398620605s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.506111145019531e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2988889217376709s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02194499969482422s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.916854858398438e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 7.62939453125e-06s
INFO | --- Analysis for bioportal-taxrank took 3.0569539070129395s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 8.845329284667969e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.31925058364868164s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.176399230957031e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-teddy took 2.977132558822632s
Availability | SPARQL endpoint availability check for Time Event Ontology took 5.364418029785156e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.3110370635986328s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020807504653930664s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008029937744140625s
Believability | Calculation of trust value for Time Event Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-teo took 2.887141227722168s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 9.679794311523438e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.3329041004180908s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003993511199951172s
Believability | Calculation of trust value for Mosquito gross anatomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tgma took 3.041445016860962s
Availability | SPARQL endpoint availability check for thesaurus took 4.744529724121094e-05s
Availability | VoID file availability check for thesaurus took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for thesaurus took 0.26316189765930176s
Reputation | Calculation of the PageRank for thesaurus took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.104873657226562e-05s
Believability | Calculation of trust value for thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.9648633003234863s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 9.059906005859375e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.000408172607421875s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.274738073348999s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003542900085449219s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.896254301071167s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.30569958686828613s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008320808410644531s
Believability | Calculation of trust value for Translational Medicine Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tmo took 3.057058572769165s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.3220851421356201s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015306472778320312s
Believability | Calculation of trust value for Plant Trait Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-to took 2.8987326622009277s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.31154417991638184s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001800060272216797s
Believability | Calculation of trust value for TOK_Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tok took 2.853019952774048s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.38690185546875e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.27470970153808594s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019550323486328125s
Believability | Calculation of trust value for Teleost taxonomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tto took 2.9628796577453613s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.27459216117858887s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.022431373596191406s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010075569152832031s
Believability | Calculation of trust value for Uber anatomy ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-uberon took 2.975494384765625s
Availability | SPARQL endpoint availability check for Units Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Units Ontology took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.28674912452697754s
Reputation | Calculation of the PageRank for Units Ontology took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002219676971435547s
Believability | Calculation of trust value for Units Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.9214670658111572s
Availability | SPARQL endpoint availability check for Units of measurement took 9.131431579589844e-05s
Availability | VoID file availability check for Units of measurement took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.3013012409210205s
Reputation | Calculation of the PageRank for Units of measurement took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00029397010803222656s
Believability | Calculation of trust value for Units of measurement took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-uo took 2.970702648162842s
Availability | SPARQL endpoint availability check for VANDF took 4.38690185546875e-05s
Availability | VoID file availability check for VANDF took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for VANDF took 0.29724621772766113s
Reputation | Calculation of the PageRank for VANDF took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for VANDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006895065307617188s
Believability | Calculation of trust value for VANDF took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-vandf took 2.8536837100982666s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.28447508811950684s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.021346330642700195s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004150867462158203s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-vao took 3.0078511238098145s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 8.96453857421875e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.00113677978515625s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2751331329345703s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006270408630371094s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-vhog took 2.9259629249572754s
Availability | SPARQL endpoint availability check for VIVO took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for VIVO took 0.2880570888519287s
Reputation | Calculation of the PageRank for VIVO took 0.021568775177001953s
Interlinking | Calculation of Degree of Connection for VIVO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003540515899658203s
Believability | Calculation of trust value for VIVO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-vivo took 2.947336196899414s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.27313756942749023s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.021457672119140625s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012359619140625s
Believability | Calculation of trust value for Vaccine Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vo took 2.9664363861083984s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 5.888938903808594e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2967674732208252s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020837783813476562s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vt took 2.969390392303467s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 9.1552734375e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.29056620597839355s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004825592041015625s
Believability | Calculation of trust value for C. elegans gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbbt took 2.946298599243164s
Availability | SPARQL endpoint availability check for C. elegans development took 9.083747863769531e-05s
Availability | VoID file availability check for C. elegans development took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.30460309982299805s
Reputation | Calculation of the PageRank for C. elegans development took 0.021176815032958984s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.410743713378906e-05s
Believability | Calculation of trust value for C. elegans development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-wbls took 2.9701390266418457s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 8.821487426757812e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.26742005348205566s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.202957153320312e-05s
Believability | Calculation of trust value for C. elegans phenotype took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.8800625801086426s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 8.940696716308594e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0010657310485839844s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.27055907249450684s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005853176116943359s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-who took 2.916999578475952s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.38690185546875e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2963693141937256s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006506443023681641s
Believability | Calculation of trust value for Xenopus anatomy and development took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-xao took 3.0267772674560547s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 9.226799011230469e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.2853982448577881s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023889541625976562s
Believability | Calculation of trust value for Experimental Conditions Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-xco took 2.949091911315918s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 9.250640869140625e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.30393171310424805s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002636909484863281s
Believability | Calculation of trust value for Yeast phenotypes took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ypo took 2.8950681686401367s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.845329284667969e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2985074520111084s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007669925689697266s
Believability | Calculation of trust value for Zebrafish anatomy and development took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-zfa took 3.011131525039673s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.458427429199219e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.00034809112548828125s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.2860283851623535s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 7.152557373046875e-06s
INFO | --- Analysis for Bioportal_link took 4.241048097610474s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.41190147399902344s
Availability | VoID file availability check for BioSamples RDF took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.3040130138397217s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.0728836059570312e-05s
INFO | --- Analysis for biosamples-rdf took 3.7495431900024414s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.2318406105041504s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0002155303955078125s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2840116024017334s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.0001125335693359375s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for bis-linked-data took 2.879971742630005s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.32337236404418945s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.076957702636719e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for bll-thesaurus took 3.759528875350952s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 0.36723780632019043s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0008046627044677734s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.3257603645324707s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.556510925292969e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for bluk-bnb took 12.031436443328857s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.2956273555755615s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006816387176513672s
Extra | Recovery of all triples for Thesaurus BNCF took 59.27605748176575s
Performance | Total latancy measurement for Thesaurus BNCF took 0.655203104019165s
Amount of data | Number of triples check for Thesaurus BNCF took 0.7003903388977051s
Interoperability | New terms check for Thesaurus BNCF took 1.4959006309509277s
Versatility | Languages check for Thesaurus BNCF took 6.939857721328735s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8979127407073975s
Security | Check HTTPS for Thesaurus BNCF took 0.09968400001525879s
Interpretability | RDF structures check for Thesaurus BNCF took 0.11523079872131348s
Versatility | Serialization formats check for Thesaurus BNCF took 0.13491106033325195s
Availability | RDF dump link check for Thesaurus BNCF took 0.11691880226135254s
License | MR license check for Thesaurus BNCF took 0.12511086463928223s
License | HR license check for Thesaurus BNCF took 0.21663856506347656s
Amount of data | Number of property check for Thesaurus BNCF took 0.12337279319763184s
Understandability | Number of label check for Thesaurus BNCF took 0.25466203689575195s
Understandability | URI regex check for Thesaurus BNCF took 0.23572635650634766s
Understandability | Vocabs check for Thesaurus BNCF took 0.13158822059631348s
Verifiability | Authors check for Thesaurus BNCF took 0.1261906623840332s
Verifiability | Publishers check for Thesaurus BNCF took 0.11707520484924316s
Performance | Throughput check for Thesaurus BNCF took 10.62585997581482s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.510185241699219e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.1271364688873291s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12111687660217285s
Interlinking | skos check for Thesaurus BNCF took 0.17659497261047363s
Interlinking | skos check for Thesaurus BNCF took 0.140303373336792s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.13437986373901367s
Currency | Creation date check for Thesaurus BNCF took 0.2530944347381592s
Currency | Modification date check for Thesaurus BNCF took 0.25248146057128906s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.792064905166626s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.12334680557250977s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.1162869930267334s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.12558484077453613s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.782649040222168s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4896831512451172s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.83199405670166s
Consistency | Disjoint class check for Thesaurus BNCF took 0.13586759567260742s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.9379611015319824s
Consistency | Misplaced classes for Thesaurus BNCF took 6.5988054275512695s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.746239900588989s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.5036864280700684s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.3724074363708496s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4771111011505127s
Security | Sign check for Thesaurus BNCF took 0.12868213653564453s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 20.60579824447632s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.5427687168121338s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.939338684082031e-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 1.2874603271484375e-05s
INFO | --- Analysis for bncf-ns took 197.0673224925995s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5909924507141113s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007417201995849609s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5841388702392578s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.7966010570526123s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.9467010498046875s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.027937173843384s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.23268699645996s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.536918878555298s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2965407371520996s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33899378776550293s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5110347270965576s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47574496269226074s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38523411750793457s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.295006275177s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38721704483032227s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8599045276641846s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.732947826385498s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4899921417236328s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3808603286743164s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.345841646194458s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.017626285552979s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.653236389160156e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3338909149169922s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34835124015808105s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36768174171447754s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3841817378997803s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.46170806884765625s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7820181846618652s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37723422050476074s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.736521244049072s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34361696243286133s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38077735900878906s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36164259910583496s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7965285778045654s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030625104904174805s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028810977935791016s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37421584129333496s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.558597564697266s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4335205554962158s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.206347942352295s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5362157821655273s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.81502914428711s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03145098686218262s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3714911937713623s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4020380973815918s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.563855171203613s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3763303756713867s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.021858692169189453s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0008256435394287109s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00014019012451171875s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.62939453125e-06s
INFO | --- Analysis for bpr took 394.93972158432007s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.96453857421875e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.33835554122924805s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02101922035217285s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 8.249282836914062e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.58306884765625e-06s
INFO | --- Analysis for brazilian-politicians took 2.8146591186523438s
Availability | SPARQL endpoint availability check for Bricklink took 5.723672389984131s
Availability | VoID file availability check for Bricklink took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2933082580566406s
Reputation | Calculation of the PageRank for Bricklink took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.842613220214844e-05s
Believability | Calculation of trust value for Bricklink took 1.1920928955078125e-05s
INFO | --- Analysis for bricklink took 18.696197748184204s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.16113042831421s
Availability | VoID file availability check for British Museum Collection took 0.0007898807525634766s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2992565631866455s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02190232276916504s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.409385681152344e-05s
Believability | Calculation of trust value for British Museum Collection took 1.3828277587890625e-05s
INFO | --- Analysis for british-museum-collection took 72.9728639125824s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 9.1552734375e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.29174208641052246s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.021322011947631836s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.790855407714844e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.2636184692382812e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.74330735206604s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.20421671867370605s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006468296051025391s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.887524366378784s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.5872468948364258s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.134376049041748s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.783418893814087s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.161849737167358s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0986824035644531s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13135910034179688s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12516331672668457s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12323331832885742s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1164543628692627s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 22.904142379760742s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11551618576049805s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.21399497985839844s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.23855042457580566s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12384915351867676s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13168859481811523s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12285757064819336s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.716461181640625s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.605552673339844e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12187814712524414s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12141704559326172s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1284029483795166s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12867426872253418s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12966346740722656s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24332070350646973s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.25153303146362305s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.727224111557007s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12282395362854004s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12671804428100586s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.127000093460083s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.072650909423828s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24886727333068848s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.499594688415527s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12340569496154785s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.042818546295166s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.949305295944214s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2512130737304688s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.333157539367676s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.802738904953003s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12096691131591797s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3582.865481853485s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.817749500274658s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02098679542541504s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.52587890625e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.0067901611328125e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 8.58306884765625e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3700.0192770957947s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.2768239974975586s
Availability | VoID file availability check for business.data.gov.uk took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2953298091888428s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.1975250244140625e-05s
Believability | Calculation of trust value for business.data.gov.uk took 8.821487426757812e-06s
INFO | --- Analysis for business-data-gov-uk took 3.196155548095703s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5220608711242676s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0006079673767089844s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.7892260551452637s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.463362216949463s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.40972328186035156s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.669687032699585s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 41.161102533340454s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3188924789428711s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.16634464263916016s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.41426968574523926s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.2974550724029541s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3239634037017822s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.39353108406066895s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.904048919677734s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3327634334564209s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.5927219390869141s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.5853955745697021s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.30685997009277344s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3531675338745117s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3722405433654785s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 13.684256076812744s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 3.409385681152344e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.30953526496887207s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.30480217933654785s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.35244059562683105s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.29367613792419434s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.31670427322387695s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6523654460906982s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.599240779876709s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.194619178771973s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.2872452735900879s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.43114662170410156s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4487311840057373s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 2.014312267303467s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03502917289733887s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.028609275817871094s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.36188769340515137s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.408583402633667s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.4000129699707031s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.7801673412323s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2598624229431152s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.447603702545166s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03274989128112793s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.2826859951019287s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.30916810035705566s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1462.0681691169739s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.4143192768096924s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02101612091064453s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.1444091796875e-05s
INFO | --- Analysis for BVMC took 1596.931478023529s
Availability | SPARQL endpoint availability check for cablegate took 1.444868803024292s
Availability | VoID file availability check for cablegate took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for cablegate took 0.3036196231842041s
Reputation | Calculation of the PageRank for cablegate took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for cablegate took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.794929504394531e-05s
Believability | Calculation of trust value for cablegate took 1.0728836059570312e-05s
INFO | --- Analysis for cablegate took 16.61786961555481s
Availability | SPARQL endpoint availability check for Calames took 0.00011134147644042969s
Availability | VoID file availability check for Calames took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Calames took 0.3049163818359375s
Reputation | Calculation of the PageRank for Calames took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for Calames took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Calames took 3.4332275390625e-05s
Believability | Calculation of trust value for Calames took 1.0728836059570312e-05s
INFO | --- Analysis for calames took 4.273228168487549s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.4534173011779785s
Availability | VoID file availability check for CaLiGraph took 0.0004611015319824219s
Extra | Recovery of all triples for CaLiGraph took 1.6295599937438965s
Performance | Total latancy measurement for CaLiGraph took 1.1530675888061523s
Amount of data | Number of triples check for CaLiGraph took 14.05096173286438s
Interoperability | New terms check for CaLiGraph took 1.9559648036956787s
Versatility | Languages check for CaLiGraph took 60.30307078361511s
Interpretability | Number of blank nodes check for CaLiGraph took 0.27011561393737793s
Security | Check HTTPS for CaLiGraph took 0.1392679214477539s
Interpretability | RDF structures check for CaLiGraph took 0.2586395740509033s
Versatility | Serialization formats check for CaLiGraph took 0.2522099018096924s
Availability | RDF dump link check for CaLiGraph took 0.2641289234161377s
License | MR license check for CaLiGraph took 0.2633554935455322s
License | HR license check for CaLiGraph took 60.303999185562134s
Amount of data | Number of property check for CaLiGraph took 0.26641345024108887s
Understandability | Number of label check for CaLiGraph took 3.3867928981781006s
Understandability | URI regex check for CaLiGraph took 0.5138673782348633s
Understandability | Vocabs check for CaLiGraph took 0.2510688304901123s
Verifiability | Authors check for CaLiGraph took 0.25318002700805664s
Verifiability | Publishers check for CaLiGraph took 0.27584099769592285s
Performance | Throughput check for CaLiGraph took 11.498691320419312s
Amount of data | Check the number of entities for CaLiGraph took 0.017742395401000977s
Verifiability | Contribs. check for CaLiGraph took 0.2517571449279785s
Interlinking | sameAs chians check for CaLiGraph took 0.6797735691070557s
Interlinking | skos check for CaLiGraph took 0.2528841495513916s
Interlinking | skos check for CaLiGraph took 0.23010563850402832s
Timeliness | dataset update frequency check for CaLiGraph took 0.26143407821655273s
Currency | Creation date check for CaLiGraph took 0.5020923614501953s
Currency | Modification date check for CaLiGraph took 0.5387387275695801s
Rep.Conc. | URIs length for CaLiGraph took 61.05626702308655s
Interoperability | New vocabularies check for CaLiGraph took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2652280330657959s
Accuracy | Check Functional Property for CaLiGraph took 0.23739361763000488s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2522456645965576s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5865030288696289s
Accuracy | Check White space in annotation for CaLiGraph took 0.02633976936340332s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05035710334777832s
Consistency | Disjoint class check for CaLiGraph took 0.251568078994751s
Consistency | Check Misplaced properties for CaLiGraph took 60.973724126815796s
Consistency | Misplaced classes for CaLiGraph took 0.5197718143463135s
Consistency | Check Ontology hijacking for CaLiGraph took 2.060486316680908s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3210244178771973s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.595757484436035s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03526735305786133s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4692363739013672s
Security | Sign check for CaLiGraph took 0.2471296787261963s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.9943687915802s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.5218591690063477s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.9073486328125e-06s
Believability | Calculation of trust value for CaLiGraph took 4.220008850097656e-05s
INFO | --- Analysis for CaLiGraph took 1448.1964406967163s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.25694918632507324s
Availability | VoID file availability check for CaLiGraph took 0.000423431396484375s
Extra | Recovery of all triples for CaLiGraph took 1.663743495941162s
Performance | Total latancy measurement for CaLiGraph took 1.1395175457000732s
Amount of data | Number of triples check for CaLiGraph took 13.617468118667603s
Interoperability | New terms check for CaLiGraph took 1.9524636268615723s
Versatility | Languages check for CaLiGraph took 60.31974792480469s
Interpretability | Number of blank nodes check for CaLiGraph took 0.24858331680297852s
Security | Check HTTPS for CaLiGraph took 0.14029979705810547s
Interpretability | RDF structures check for CaLiGraph took 0.25464439392089844s
Versatility | Serialization formats check for CaLiGraph took 0.266190767288208s
Availability | RDF dump link check for CaLiGraph took 0.2594411373138428s
License | MR license check for CaLiGraph took 0.25238609313964844s
License | HR license check for CaLiGraph took 60.29795980453491s
Amount of data | Number of property check for CaLiGraph took 0.2744748592376709s
Understandability | Number of label check for CaLiGraph took 3.2694108486175537s
Understandability | URI regex check for CaLiGraph took 0.5231404304504395s
Understandability | Vocabs check for CaLiGraph took 0.2718777656555176s
Verifiability | Authors check for CaLiGraph took 0.2608604431152344s
Verifiability | Publishers check for CaLiGraph took 0.26952242851257324s
Performance | Throughput check for CaLiGraph took 11.592649221420288s
Amount of data | Check the number of entities for CaLiGraph took 0.015825510025024414s
Verifiability | Contribs. check for CaLiGraph took 0.2418961524963379s
Interlinking | sameAs chians check for CaLiGraph took 0.6557004451751709s
Interlinking | skos check for CaLiGraph took 0.2682077884674072s
Interlinking | skos check for CaLiGraph took 0.23030352592468262s
Timeliness | dataset update frequency check for CaLiGraph took 0.2639021873474121s
Currency | Creation date check for CaLiGraph took 0.5345783233642578s
Currency | Modification date check for CaLiGraph took 0.520869255065918s
Rep.Conc. | URIs length for CaLiGraph took 60.9900918006897s
Interoperability | New vocabularies check for CaLiGraph took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2672581672668457s
Accuracy | Check Functional Property for CaLiGraph took 0.2686924934387207s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.25634026527404785s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5595681667327881s
Accuracy | Check White space in annotation for CaLiGraph took 0.026288747787475586s
Accuracy | Check Datatype consistency for CaLiGraph took 0.049337148666381836s
Consistency | Disjoint class check for CaLiGraph took 0.24322032928466797s
Consistency | Check Misplaced properties for CaLiGraph took 61.13646674156189s
Consistency | Misplaced classes for CaLiGraph took 0.5209388732910156s
Consistency | Check Ontology hijacking for CaLiGraph took 2.033473253250122s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2668182849884033s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.61065697669983s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.030297279357910156s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4368748664855957s
Security | Sign check for CaLiGraph took 0.2463371753692627s
Availability | Check URIs Dereferenciability for CaLiGraph took 10.675599575042725s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.3924093246459961s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020732641220092773s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.176399230957031e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 2.1457672119140625e-06s
Believability | Calculation of trust value for CaLiGraph took 1.0728836059570312e-05s
INFO | --- Analysis for caligraph took 1738.22838306427s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.019844532012939453s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.303816556930542s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02171945571899414s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.981590270996094e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.33514404296875e-05s
INFO | --- Analysis for cap-italy-rdf took 2.840076208114624s
Availability | SPARQL endpoint availability check for person took 0.00011467933654785156s
Availability | VoID file availability check for person took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for person took 0.298870325088501s
Reputation | Calculation of the PageRank for person took 0.0210115909576416s
Interlinking | Calculation of Degree of Connection for person took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for person took 0.0009212493896484375s
Interlinking | Calculation of Clustering coefficient for person took 3.457069396972656e-05s
Believability | Calculation of trust value for person took 1.1920928955078125e-05s
INFO | --- Analysis for card took 2.749319553375244s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 9.012222290039062e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.31275391578674316s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02211594581604004s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.458427429199219e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.1646645069122314s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.5112628936767578s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00047779083251953125s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 111.22999310493469s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9852967262268066s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.413992404937744s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.314898014068604s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.18625235557556s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.063096284866333s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.3228268623352051s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 6.762314796447754s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.31860852241516113s
License | MR license check for Norway catch records dataset @PSNC took 0.633047342300415s
License | HR license check for Norway catch records dataset @PSNC took 300.2502324581146s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.20523905754089355s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.282925844192505s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.8791115283966064s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.4409341812133789s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.19317221641540527s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.22626566886901855s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.429192066192627s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.081031799316406e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.1810622215270996s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.18906760215759277s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.5171182155609131s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.42885446548461914s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 4.3297483921051025s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.45125555992126465s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.23831963539123535s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 146.30703139305115s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.18041229248046875s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.32746124267578125s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.4414041042327881s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 37.74978470802307s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6479063034057617s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.6028852462768555s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.19817137718200684s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 86.4190993309021s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.325045108795166s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 34.45388889312744s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.4047930240631104s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 87.55860614776611s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.8061957359313965s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5408236980438232s
Security | Sign check for Norway catch records dataset @PSNC took 1.191953420639038s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 10.824379682540894s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.4258744716644287s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.021391630172729492s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 0.00011491775512695312s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2252.1701085567474s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.560585021972656e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2860374450683594s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020913362503051758s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.918212890625e-05s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2874603271484375e-05s
INFO | --- Analysis for ce4r took 34.70932483673096s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6302249431610107s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005180835723876953s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.116377830505371s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.8884470462799072s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28060460090637207s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.7096409797668457s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.137856006622314s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1732633113861084s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31029820442199707s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18104314804077148s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16439175605773926s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24055719375610352s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3376004695892334s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17211675643920898s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3025226593017578s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3841855525970459s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1726551055908203s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19347906112670898s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20186638832092285s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 11.343719244003296s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.2479248046875e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2620859146118164s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18186187744140625s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 1.0146598815917969s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1562652587890625s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19812273979187012s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6935350894927979s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.49918174743652344s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.0804595947265625s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1717085838317871s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 3.0405428409576416s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028603792190551758s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.030715227127075195s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4825327396392822s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2591981887817383s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9186859130859375s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.269881248474121s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.470094919204712s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.030696392059326172s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.21369361877441406s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14815759658813477s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2517.021684408188s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.9383823871612549s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.021593809127807617s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 2.384185791015625e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.1205673217773438e-05s
INFO | --- Analysis for ceo took 2646.4919390678406s
Availability | SPARQL endpoint availability check for Chat Game corpus took 8.988380432128906e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.3112831115722656s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.695487976074219e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.1205673217773438e-05s
INFO | --- Analysis for chat-game-corpus took 13.223030805587769s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 8.845329284667969e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008759498596191406s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.32118892669677734s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02078104019165039s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.103515625e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.3113021850585938e-05s
INFO | --- Analysis for chem2bio2rdf took 133.97997117042542s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.6132047176361084s
Availability | VoID file availability check for ChEMBL RDF took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.3188459873199463s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.982948303222656e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.3589859008789062e-05s
INFO | --- Analysis for chembl-rdf took 4.097759246826172s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.1267626285552979s
Availability | VoID file availability check for chemdb  dataset took 0.0005271434783935547s
Extra | Recovery of all triples for chemdb  dataset took 4.836834669113159s
Performance | Total latancy measurement for chemdb  dataset took 2.5181050300598145s
Amount of data | Number of triples check for chemdb  dataset took 0.5397636890411377s
Interoperability | New terms check for chemdb  dataset took 3.4238171577453613s
Versatility | Languages check for chemdb  dataset took 21.90733790397644s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5270133018493652s
Interpretability | RDF structures check for chemdb  dataset took 0.528329610824585s
Versatility | Serialization formats check for chemdb  dataset took 0.5878419876098633s
Availability | RDF dump link check for chemdb  dataset took 0.5032267570495605s
License | MR license check for chemdb  dataset took 0.6455826759338379s
License | HR license check for chemdb  dataset took 3.0678529739379883s
Amount of data | Number of property check for chemdb  dataset took 0.5295767784118652s
Understandability | Number of label check for chemdb  dataset took 1.020540475845337s
Understandability | URI regex check for chemdb  dataset took 0.9974350929260254s
Understandability | Vocabs check for chemdb  dataset took 0.5001418590545654s
Verifiability | Authors check for chemdb  dataset took 0.6451234817504883s
Verifiability | Publishers check for chemdb  dataset took 0.49532008171081543s
Performance | Throughput check for chemdb  dataset took 12.54435420036316s
Amount of data | Check the number of entities for chemdb  dataset took 6.723403930664062e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.5073196887969971s
Interlinking | sameAs chians check for chemdb  dataset took 0.5962285995483398s
Interlinking | skos check for chemdb  dataset took 0.6085491180419922s
Interlinking | skos check for chemdb  dataset took 0.5006141662597656s
Timeliness | dataset update frequency check for chemdb  dataset took 0.49629878997802734s
Currency | Creation date check for chemdb  dataset took 1.0363471508026123s
Currency | Modification date check for chemdb  dataset took 1.0296461582183838s
Rep.Conc. | URIs length for chemdb  dataset took 2.8998560905456543s
Interoperability | New vocabularies check for chemdb  dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5186312198638916s
Accuracy | Check Functional Property for chemdb  dataset took 0.5346364974975586s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.5038256645202637s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.134632110595703s
Accuracy | Check White space in annotation for chemdb  dataset took 0.03016376495361328s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03565073013305664s
Consistency | Disjoint class check for chemdb  dataset took 0.5357708930969238s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2437808513641357s
Consistency | Misplaced classes for chemdb  dataset took 0.6085853576660156s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.4252002239227295s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.2683155536651611s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.9933733940124512s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.032547712326049805s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5407238006591797s
Security | Sign check for chemdb  dataset took 0.7135226726531982s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2505.5452353954315s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.540564775466919s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021520137786865234s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.343292236328125e-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 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-basicInfo took 4769.533264636993s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5284180641174316s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00028443336486816406s
Extra | Recovery of all triples for chemdb estimated properties dataset took 4.929965496063232s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.505784749984741s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.545708417892456s
Interoperability | New terms check for chemdb estimated properties dataset took 3.4395172595977783s
Versatility | Languages check for chemdb estimated properties dataset took 22.572779178619385s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.519794225692749s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.521355390548706s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.5284690856933594s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.49963903427124023s
License | MR license check for chemdb estimated properties dataset took 0.6673305034637451s
License | HR license check for chemdb estimated properties dataset took 3.1279852390289307s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5270190238952637s
Understandability | Number of label check for chemdb estimated properties dataset took 0.5977368354797363s
Understandability | URI regex check for chemdb estimated properties dataset took 1.0297198295593262s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.5034780502319336s
Verifiability | Authors check for chemdb estimated properties dataset took 0.5008621215820312s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.495438814163208s
Performance | Throughput check for chemdb estimated properties dataset took 12.047180414199829s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 6.937980651855469e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.504103422164917s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.5231063365936279s
Interlinking | skos check for chemdb estimated properties dataset took 0.49320125579833984s
Interlinking | skos check for chemdb estimated properties dataset took 0.4990084171295166s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.5010251998901367s
Currency | Creation date check for chemdb estimated properties dataset took 1.0265858173370361s
Currency | Modification date check for chemdb estimated properties dataset took 1.0188050270080566s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 2.9412267208099365s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.4851875305175781s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.5306885242462158s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.5042314529418945s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 2.1271908283233643s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.030147552490234375s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.0329744815826416s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.49439120292663574s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2212471961975098s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6152722835540771s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.4618752002716064s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.277038335800171s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9704339504241943s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03314065933227539s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.531536340713501s
Security | Sign check for chemdb estimated properties dataset took 0.5029792785644531s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2501.655401468277s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.4939730167388916s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02117776870727539s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 5.4836273193359375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.33514404296875e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 5024.332629442215s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5236964225769043s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0004723072052001953s
Extra | Recovery of all triples for chemdb phase transition dataset took 4.9856109619140625s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.4829182624816895s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5621721744537354s
Interoperability | New terms check for chemdb phase transition dataset took 3.426861524581909s
Versatility | Languages check for chemdb phase transition dataset took 22.405044555664062s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5249724388122559s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5352258682250977s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.5304656028747559s
Availability | RDF dump link check for chemdb phase transition dataset took 0.5036628246307373s
License | MR license check for chemdb phase transition dataset took 0.5011069774627686s
License | HR license check for chemdb phase transition dataset took 3.0631606578826904s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5284731388092041s
Understandability | Number of label check for chemdb phase transition dataset took 0.5355262756347656s
Understandability | URI regex check for chemdb phase transition dataset took 0.9805877208709717s
Understandability | Vocabs check for chemdb phase transition dataset took 0.5005145072937012s
Verifiability | Authors check for chemdb phase transition dataset took 0.5007307529449463s
Verifiability | Publishers check for chemdb phase transition dataset took 0.49572324752807617s
Performance | Throughput check for chemdb phase transition dataset took 12.5189790725708s
Amount of data | Check the number of entities for chemdb phase transition dataset took 6.937980651855469e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.49616050720214844s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.5267236232757568s
Interlinking | skos check for chemdb phase transition dataset took 0.5046677589416504s
Interlinking | skos check for chemdb phase transition dataset took 0.5058491230010986s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.49864888191223145s
Currency | Creation date check for chemdb phase transition dataset took 1.034759521484375s
Currency | Modification date check for chemdb phase transition dataset took 1.027195930480957s
Rep.Conc. | URIs length for chemdb phase transition dataset took 2.9791665077209473s
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.49155282974243164s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.5276777744293213s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.5035910606384277s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 2.1868016719818115s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030237913131713867s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03389120101928711s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.48175048828125s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2419602870941162s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6275486946105957s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.442139148712158s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.317326307296753s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.017989158630371s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.0347442626953125s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5214860439300537s
Security | Sign check for chemdb phase transition dataset took 0.5021171569824219s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2497.9548904895782s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.5181481838226318s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021010160446166992s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.2159347534179688e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4732.705892086029s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5123956203460693s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0002865791320800781s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 4.94174861907959s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.517240285873413s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.558016300201416s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.4271154403686523s
Versatility | Languages check for chemdb thermochemistry dataset took 23.486191034317017s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5187342166900635s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5173375606536865s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5339415073394775s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.48465824127197266s
License | MR license check for chemdb thermochemistry dataset took 0.5049502849578857s
License | HR license check for chemdb thermochemistry dataset took 3.129676580429077s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5334908962249756s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.536480188369751s
Understandability | URI regex check for chemdb thermochemistry dataset took 0.993765115737915s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.5036795139312744s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.5000288486480713s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.4958798885345459s
Performance | Throughput check for chemdb thermochemistry dataset took 13.511417388916016s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 6.937980651855469e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.503972053527832s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.523874044418335s
Interlinking | skos check for chemdb thermochemistry dataset took 0.4894261360168457s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5030426979064941s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.4959433078765869s
Currency | Creation date check for chemdb thermochemistry dataset took 1.026435136795044s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0122241973876953s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 2.9090771675109863s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.5079412460327148s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5294926166534424s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.4877958297729492s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.161288022994995s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.030571699142456055s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.034143686294555664s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.4961075782775879s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2341175079345703s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.593066930770874s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.424791097640991s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.3272087574005127s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.0297460556030273s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03455328941345215s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5238299369812012s
Security | Sign check for chemdb thermochemistry dataset took 0.485931396484375s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2504.7131524086s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.5247161388397217s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.3828277587890625e-05s
INFO | --- Analysis for chemdb-thermochemistry took 4717.7249665260315s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 9.059906005859375e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.2839317321777344s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.022131919860839844s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.2159347534179688e-05s
INFO | --- Analysis for chempedia-rdf took 9.814476251602173s
Availability | SPARQL endpoint availability check for Chiman Maru took 8.606910705566406e-05s
Availability | VoID file availability check for Chiman Maru took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.2749619483947754s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.600120544433594e-05s
Believability | Calculation of trust value for Chiman Maru took 1.0013580322265625e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.6175620555877686s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.22777128219604s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.38106703758239746s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.022007465362548828s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.4809112548828125e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 798.3344411849976s
Availability | SPARQL endpoint availability check for Chronicling America took 9.083747863769531e-05s
Availability | VoID file availability check for Chronicling America took 0.0007731914520263672s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.4516334533691406s
Reputation | Calculation of the PageRank for Chronicling America took 0.023302078247070312s
Interlinking | Calculation of Degree of Connection for Chronicling America took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00011110305786132812s
Believability | Calculation of trust value for Chronicling America took 1.1920928955078125e-05s
INFO | --- Analysis for chronicling-america took 328.67713832855225s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.6835827827453613s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.000667572021484375s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 86.82693791389465s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.667482614517212s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 2.2943828105926514s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.6040163040161133s
Versatility | Languages check for Cultural Heritage Thesaurus took 11.839863777160645s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 3.6405019760131836s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.38817310333251953s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3544743061065674s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.720638751983643s
License | MR license check for Cultural Heritage Thesaurus took 0.3832228183746338s
License | HR license check for Cultural Heritage Thesaurus took 0.7989387512207031s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3328213691711426s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.7309854030609131s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6339116096496582s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.36092591285705566s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.33829689025878906s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.2823162078857422s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.959489822387695s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.559226989746094e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.304884672164917s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.2939300537109375s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.37125158309936523s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.385143518447876s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.36808300018310547s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.7740569114685059s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6001555919647217s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 28.95837640762329s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 0.9225964546203613s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3442378044128418s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.301436185836792s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.33376622200012207s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 7.340027570724487s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21966028213500977s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.39402031898498535s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 4.4630913734436035s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3664705753326416s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 8.251702547073364s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 3.705754518508911s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001678466796875s
Security | Sign check for Cultural Heritage Thesaurus took 0.34159135818481445s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 365.4281005859375s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.36954498291015625s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.027317523956298828s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00010442733764648438s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.3971226215362549s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 5.245208740234375e-06s
INFO | --- Analysis for cht took 595.2924144268036s
Availability | SPARQL endpoint availability check for ciard-ring took 9.393692016601562e-05s
Availability | VoID file availability check for ciard-ring took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.3029177188873291s
Reputation | Calculation of the PageRank for ciard-ring took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.5299530029296875e-05s
Believability | Calculation of trust value for ciard-ring took 5.0067901611328125e-06s
INFO | --- Analysis for ciard-ring took 12.562241315841675s
Availability | SPARQL endpoint availability check for Cine Figure took 9.34600830078125e-05s
Availability | VoID file availability check for Cine Figure took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.31224799156188965s
Reputation | Calculation of the PageRank for Cine Figure took 0.02288031578063965s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.482269287109375e-05s
Believability | Calculation of trust value for Cine Figure took 1.0013580322265625e-05s
INFO | --- Analysis for Cine_Figure took 2.7955403327941895s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 2.3635528087615967s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.3191368579864502s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.649162292480469e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.5020370483398438e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 11.357756614685059s
Availability | SPARQL endpoint availability check for CIPFA took 8.916854858398438e-05s
Availability | VoID file availability check for CIPFA took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for CIPFA took 0.26460719108581543s
Reputation | Calculation of the PageRank for CIPFA took 0.021410465240478516s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.528594970703125e-05s
Believability | Calculation of trust value for CIPFA took 8.344650268554688e-06s
INFO | --- Analysis for cipfa took 2.70304274559021s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.04148244857788s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0008528232574462891s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.3048248291015625s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003921985626220703s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.1920928955078125e-05s
INFO | --- Analysis for ckan took 263.00219988822937s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6830735206604004s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.28905558586120605s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.172325134277344e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for CLaSSES took 4.674547910690308s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 9.036064147949219e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.29121947288513184s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02310013771057129s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.4332275390625e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.0728836059570312e-05s
INFO | --- Analysis for classical_temples took 5.0198423862457275s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.1155388355255127s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.28903889656066895s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.535385131835938e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 9.775161743164062e-06s
INFO | --- Analysis for clean-energy-data-reegle took 5.694498538970947s
Availability | SPARQL endpoint availability check for CLLD-afbo took 9.202957153320312e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0003845691680908203s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.30208539962768555s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.296966552734375e-05s
Believability | Calculation of trust value for CLLD-afbo took 7.152557373046875e-06s
INFO | --- Analysis for clld-afbo took 8.588982820510864s
Availability | SPARQL endpoint availability check for CLLD-APICS took 9.274482727050781e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.3019297122955322s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 8.487701416015625e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.049041748046875e-05s
INFO | --- Analysis for clld-apics took 5.267388105392456s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.458427429199219e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2799503803253174s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.021613121032714844s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.076957702636719e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.1682510375976562e-05s
INFO | --- Analysis for clld-ewave took 3.716127395629883s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.654594421386719e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.27353405952453613s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010204315185546875s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.3828277587890625e-05s
INFO | --- Analysis for clld-glottolog took 3.687819719314575s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.506111145019531e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.27882814407348633s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.130073547363281e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 2.193450927734375e-05s
INFO | --- Analysis for clld-phoible took 3.7011501789093018s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.28452181816101074s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.022702693939208984s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0011622905731201172s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 9.894371032714844e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.33514404296875e-05s
INFO | --- Analysis for clld-sails took 3.8741533756256104s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.506111145019531e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2923457622528076s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.177757263183594e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.430511474609375e-05s
INFO | --- Analysis for clld-wals took 3.817441701889038s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.301816463470459s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.022411108016967773s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.748603820800781e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.239776611328125e-05s
INFO | --- Analysis for clld-wold took 3.7854630947113037s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.1678142547607422s
Availability | VoID file availability check for Cooperation Databank took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.26470112800598145s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.022725343704223633s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.695487976074219e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.049041748046875e-05s
INFO | --- Analysis for CoDa took 2.7666945457458496s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.424614667892456s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.27904629707336426s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 8.344650268554688e-06s
INFO | --- Analysis for coins-openuplabs took 4.145702838897705s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.4395933151245117s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.30199289321899414s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.021580219268798828s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.416175842285156e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 9.775161743164062e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.561760902404785s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.19946503639221191s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.3033909797668457s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.029273986816406e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for colinda took 3.07562518119812s
Availability | SPARQL endpoint availability check for CN  2012 took 25.9568133354187s
Availability | VoID file availability check for CN  2012 took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.34107184410095215s
Reputation | Calculation of the PageRank for CN  2012 took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.363059997558594e-05s
Believability | Calculation of trust value for CN  2012 took 8.58306884765625e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 125.09058403968811s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.47461462020874023s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2964446544647217s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.022958040237426758s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0009236335754394531s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.363059997558594e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for CompHistSem took 4.154686212539673s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.0994207859039307s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0007774829864501953s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2973344326019287s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.5299530029296875e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.3828277587890625e-05s
INFO | --- Analysis for comsode-d3-2 took 8.48000955581665s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 9.1552734375e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.33833885192871094s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.021848678588867188s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.606910705566406e-05s
Believability | Calculation of trust value for 2011 US Congress People took 9.775161743164062e-06s
INFO | --- Analysis for congresspeople took 3.525315046310425s
Availability | SPARQL endpoint availability check for MIMO took 0.29644203186035156s
Availability | VoID file availability check for MIMO took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for MIMO took 0.27918577194213867s
Reputation | Calculation of the PageRank for MIMO took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for MIMO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.2874603271484375e-05s
Believability | Calculation of trust value for MIMO took 1.1682510375976562e-05s
INFO | --- Analysis for CONNECTED took 4.1420392990112305s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.76837158203125e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.32892799377441406s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.147125244140625e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.0251998901367188e-05s
INFO | --- Analysis for Copyright_Free_Music took 3.556190252304077s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 0.00012803077697753906s
Availability | VoID file availability check for CopyrightTermBank took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.3039374351501465s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.022289037704467773s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.104873657226562e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.3113021850585938e-05s
INFO | --- Analysis for copyrighttermbank took 34.11291980743408s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.9945404529571533s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.30660152435302734s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.886222839355469e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.1444091796875e-05s
INFO | --- Analysis for core took 8.114068984985352s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.6067469120025635s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005695819854736328s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 105.15666460990906s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9986374378204346s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.269270896911621s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.883324384689331s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2483365535736s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.4107346534729004s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.36757588386535645s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 9.440776109695435s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.38346433639526367s
License | MR license check for Corine linked dataset @PSNC took 0.8841245174407959s
License | HR license check for Corine linked dataset @PSNC took 300.1824357509613s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.21223235130310059s
Understandability | Number of label check for Corine linked dataset @PSNC took 3.1681251525878906s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.2217283248901367s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.5925095081329346s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.2098686695098877s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.23419928550720215s
Performance | Throughput check for Corine linked dataset @PSNC took 11.624583721160889s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.772445678710938e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.20201992988586426s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.19933605194091797s
Interlinking | skos check for Corine linked dataset @PSNC took 0.475618839263916s
Interlinking | skos check for Corine linked dataset @PSNC took 0.5281949043273926s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 3.874525785446167s
Currency | Creation date check for Corine linked dataset @PSNC took 0.4892997741699219s
Currency | Modification date check for Corine linked dataset @PSNC took 0.2344210147857666s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 144.4579794406891s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.2001047134399414s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.4672107696533203s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.44136953353881836s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 35.885560750961304s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6762423515319824s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.6398000717163086s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.1965177059173584s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 87.77136564254761s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.29010796546936s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 30.883211851119995s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.4132723808288574s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 89.00877046585083s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.8033065795898438s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.6003637313842773s
Security | Sign check for Corine linked dataset @PSNC took 1.4835374355316162s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.246678829193115s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 5.815121412277222s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.026119232177734375s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.410743713378906e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Corine_linked_dataset took 2250.6380863189697s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.553794860839844e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.30838727951049805s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.984306335449219e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.3113021850585938e-05s
INFO | --- Analysis for cornetto took 13.448735475540161s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.16574573516845703s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0004703998565673828s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 201.35892367362976s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5538837909698486s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 77.88802075386047s
Interoperability | New terms check for Corporate Body Named Authority List  took 57.13357448577881s
Versatility | Languages check for Corporate Body Named Authority List  took 300.0632243156433s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 60.59327030181885s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.377011775970459s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.7232496738433838s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 3.9138169288635254s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.20385122299194336s
License | MR license check for Corporate Body Named Authority List  took 0.3848879337310791s
License | HR license check for Corporate Body Named Authority List  took 300.0771563053131s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.18510079383850098s
Understandability | Number of label check for Corporate Body Named Authority List  took 2.494246482849121s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.39556121826171875s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.10008525848388672s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.366579532623291s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2534365653991699s
Performance | Throughput check for Corporate Body Named Authority List  took 10.836562156677246s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.224082946777344e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.1969611644744873s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.097735643386841s
Interlinking | skos check for Corporate Body Named Authority List  took 0.34611082077026367s
Interlinking | skos check for Corporate Body Named Authority List  took 0.38144445419311523s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.2729332447052002s
Currency | Creation date check for Corporate Body Named Authority List  took 0.5724804401397705s
Currency | Modification date check for Corporate Body Named Authority List  took 0.2343580722808838s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 407.63924837112427s
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.27008533477783203s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.1846144199371338s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.17462539672851562s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 41.159544706344604s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.164783239364624s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.609008550643921s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.16602540016174316s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4630546569824s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.417219400405884s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 37.63530611991882s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.7214088439941406s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.427695274353s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.086582660675049s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.3686704635620117s
Security | Sign check for Corporate Body Named Authority List  took 0.4268941879272461s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 11.550530672073364s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.7775363922119141s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02384209632873535s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 7.748603820800781e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 2.86102294921875e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.621246337890625e-05s
INFO | --- Analysis for corporate-body took 14876.71780204773s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.694542407989502s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.3362612724304199s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for CorpusFibonacci took 4.708699941635132s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.1289992332458496s
Availability | VoID file availability check for Country Name Authority List took 0.0006916522979736328s
Extra | Recovery of all triples for Country Name Authority List took 158.33247828483582s
Performance | Total latancy measurement for Country Name Authority List took 0.5801348686218262s
Amount of data | Number of triples check for Country Name Authority List took 44.11119484901428s
Interoperability | New terms check for Country Name Authority List took 56.385289669036865s
Versatility | Languages check for Country Name Authority List took 300.1290371417999s
Interpretability | Number of blank nodes check for Country Name Authority List took 15.662904262542725s
Security | Check HTTPS for Country Name Authority List took 0.3545675277709961s
Interpretability | RDF structures check for Country Name Authority List took 0.29262876510620117s
Versatility | Serialization formats check for Country Name Authority List took 3.98549485206604s
Availability | RDF dump link check for Country Name Authority List took 0.20243525505065918s
License | MR license check for Country Name Authority List took 0.24404001235961914s
License | HR license check for Country Name Authority List took 300.0716142654419s
Amount of data | Number of property check for Country Name Authority List took 0.1753826141357422s
Understandability | Number of label check for Country Name Authority List took 1.5970406532287598s
Understandability | URI regex check for Country Name Authority List took 0.46988368034362793s
Understandability | Vocabs check for Country Name Authority List took 0.09194135665893555s
Verifiability | Authors check for Country Name Authority List took 0.2531585693359375s
Verifiability | Publishers check for Country Name Authority List took 0.2121884822845459s
Performance | Throughput check for Country Name Authority List took 10.573331594467163s
Amount of data | Check the number of entities for Country Name Authority List took 6.222724914550781e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.20080780982971191s
Interlinking | sameAs chians check for Country Name Authority List took 6.973627805709839s
Interlinking | skos check for Country Name Authority List took 0.4002044200897217s
Interlinking | skos check for Country Name Authority List took 0.2748100757598877s
Timeliness | dataset update frequency check for Country Name Authority List took 0.3030252456665039s
Currency | Creation date check for Country Name Authority List took 0.3433797359466553s
Currency | Modification date check for Country Name Authority List took 0.16573286056518555s
Rep.Conc. | URIs length for Country Name Authority List took 409.79522347450256s
Interoperability | New vocabularies check for Country Name Authority List took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.16983270645141602s
Accuracy | Check Functional Property for Country Name Authority List took 0.1954658031463623s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.1753849983215332s
Accuracy | Check Empty annotation labels for Country Name Authority List took 39.733176469802856s
Accuracy | Check White space in annotation for Country Name Authority List took 3.1621038913726807s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6090235710144043s
Consistency | Disjoint class check for Country Name Authority List took 0.14820408821105957s
Consistency | Check Misplaced properties for Country Name Authority List took 300.31901693344116s
Consistency | Misplaced classes for Country Name Authority List took 8.422638654708862s
Consistency | Check Ontology hijacking for Country Name Authority List took 35.73555636405945s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.7330553531646729s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.444721698761s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.131561756134033s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.40679407119750977s
Security | Sign check for Country Name Authority List took 0.15375328063964844s
Availability | Check URIs Dereferenciability for Country Name Authority List took 10.626168489456177s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.090163230895996s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.02089858055114746s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.6689300537109375e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.3589859008789062e-05s
INFO | --- Analysis for country-authority-list took 15276.930386781693s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.07969117164611816s
Availability | VoID file availability check for Courts thesaurus took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2895240783691406s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.021594762802124023s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.961822509765625e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for courts-thesaurus took 2.811786651611328s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.432286739349365s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.30166149139404297s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.344650268554688e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for Covid-on-the-Web took 55.42946219444275s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.506972312927246s
Availability | VoID file availability check for CPA 2008 took 0.0008890628814697266s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.33107471466064453s
Reputation | Calculation of the PageRank for CPA 2008 took 0.021268606185913086s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.6716461181640625e-05s
Believability | Calculation of trust value for CPA 2008 took 9.059906005859375e-06s
INFO | --- Analysis for cpa-2008 took 124.639315366745s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.3489675521850586s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005016326904296875s
Extra | Recovery of all triples for Cooperative Patent Classification took 27.243799686431885s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.073456048965454s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.19185209274292s
Versatility | Languages check for Cooperative Patent Classification took 100.15886735916138s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.20509243011475s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.2525365352630615s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.3168196678161621s
Availability | RDF dump link check for Cooperative Patent Classification took 0.2839999198913574s
License | MR license check for Cooperative Patent Classification took 0.3239707946777344s
License | HR license check for Cooperative Patent Classification took 90.18662118911743s
Amount of data | Number of property check for Cooperative Patent Classification took 0.17847537994384766s
Understandability | Number of label check for Cooperative Patent Classification took 90.24407649040222s
Understandability | URI regex check for Cooperative Patent Classification took 0.5203485488891602s
Understandability | Vocabs check for Cooperative Patent Classification took 0.23174238204956055s
Verifiability | Authors check for Cooperative Patent Classification took 0.22362470626831055s
Verifiability | Publishers check for Cooperative Patent Classification took 0.26041603088378906s
Performance | Throughput check for Cooperative Patent Classification took 11.087312936782837s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.605552673339844e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.2293081283569336s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.16451334953308105s
Interlinking | skos check for Cooperative Patent Classification took 0.17243313789367676s
Interlinking | skos check for Cooperative Patent Classification took 0.17269611358642578s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.2160930633544922s
Currency | Creation date check for Cooperative Patent Classification took 0.39603257179260254s
Currency | Modification date check for Cooperative Patent Classification took 0.3889927864074707s
Rep.Conc. | URIs length for Cooperative Patent Classification took 132.64332056045532s
Interoperability | New vocabularies check for Cooperative Patent Classification took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.31834840774536133s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 17.889132499694824s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9719362258911133s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.740450382232666s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.2494065761566162s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.41459608078003s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 26.2346408367157s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.5688786506652832s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.64473938941956s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8901119232177734s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.3219010829925537s
Security | Sign check for Cooperative Patent Classification took 0.19027304649353027s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 2.148322105407715s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.4526708126068115s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.020961523056030273s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.9073486328125e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.2159347534179688e-05s
INFO | --- Analysis for CPC took 1196.1097841262817s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.229113817214966s
Availability | VoID file availability check for CPC 2008 took 0.0008642673492431641s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.39667439460754395s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020753860473632812s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.504753112792969e-05s
Believability | Calculation of trust value for CPC 2008 took 9.5367431640625e-06s
INFO | --- Analysis for cpc-2008 took 124.27047824859619s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.9831485748291s
Availability | VoID file availability check for CPV  2003 took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3582417964935303s
Reputation | Calculation of the PageRank for CPV  2003 took 0.021762609481811523s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0008237361907958984s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 5.0067901611328125e-05s
Believability | Calculation of trust value for CPV  2003 took 5.0067901611328125e-06s
INFO | --- Analysis for cpv-2003 took 114.61523175239563s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.70268487930298s
Availability | VoID file availability check for CPV 2008 took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.3016927242279053s
Reputation | Calculation of the PageRank for CPV 2008 took 0.02156352996826172s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0013685226440429688s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 7.009506225585938e-05s
Believability | Calculation of trust value for CPV 2008 took 5.245208740234375e-06s
INFO | --- Analysis for cpv-2008 took 124.17514252662659s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.2544467449188s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.3311593532562256s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.021227359771728516s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.506111145019531e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.1920928955078125e-05s
INFO | --- Analysis for crowdsourcing-fb took 535.2747356891632s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.740918397903442s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.3912785053253174s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.021021366119384766s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.001018524169921875s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 7.176399230957031e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.0967254638671875e-05s
INFO | --- Analysis for ctic-public-dataset took 44.483433961868286s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.37186551094055176s
Availability | VoID file availability check for CulturaLinkedData took 0.0005228519439697266s
Extra | Recovery of all triples for CulturaLinkedData took 140.27762055397034s
Performance | Total latancy measurement for CulturaLinkedData took 2.673673152923584s
Amount of data | Number of triples check for CulturaLinkedData took 2.5518686771392822s
Interoperability | New terms check for CulturaLinkedData took 4.157667875289917s
Versatility | Languages check for CulturaLinkedData took 63.485894441604614s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.0186405181884766s
Interpretability | RDF structures check for CulturaLinkedData took 0.6603024005889893s
Versatility | Serialization formats check for CulturaLinkedData took 2.351686716079712s
Availability | RDF dump link check for CulturaLinkedData took 0.2450413703918457s
License | MR license check for CulturaLinkedData took 2.5929174423217773s
License | HR license check for CulturaLinkedData took 60.753798723220825s
Amount of data | Number of property check for CulturaLinkedData took 0.20577287673950195s
Understandability | Number of label check for CulturaLinkedData took 1.047236680984497s
Understandability | URI regex check for CulturaLinkedData took 0.5941517353057861s
Understandability | Vocabs check for CulturaLinkedData took 0.28316378593444824s
Verifiability | Authors check for CulturaLinkedData took 2.057016134262085s
Verifiability | Publishers check for CulturaLinkedData took 2.1246659755706787s
Performance | Throughput check for CulturaLinkedData took 20.62822198867798s
Amount of data | Check the number of entities for CulturaLinkedData took 8.58306884765625e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.25820088386535645s
Interlinking | sameAs chians check for CulturaLinkedData took 2.2328951358795166s
Interlinking | skos check for CulturaLinkedData took 2.2902681827545166s
Interlinking | skos check for CulturaLinkedData took 0.1687922477722168s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.3070347309112549s
Currency | Creation date check for CulturaLinkedData took 0.4511580467224121s
Currency | Modification date check for CulturaLinkedData took 0.3702726364135742s
Rep.Conc. | URIs length for CulturaLinkedData took 55.74223351478577s
Interoperability | New vocabularies check for CulturaLinkedData took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.198272705078125s
Accuracy | Check Functional Property for CulturaLinkedData took 0.17526769638061523s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 2.024789571762085s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 43.59294080734253s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6152939796447754s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.291858196258545s
Consistency | Disjoint class check for CulturaLinkedData took 0.22901105880737305s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.219697713851929s
Consistency | Misplaced classes for CulturaLinkedData took 5.9800286293029785s
Consistency | Check Ontology hijacking for CulturaLinkedData took 45.12501406669617s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3759093284606934s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 10.070718765258789s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.4152147769927979s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 2.0062975883483887s
Security | Sign check for CulturaLinkedData took 2.8008408546447754s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 11.185861587524414s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.36906957626342773s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020906925201416016s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.409385681152344e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 6.198883056640625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.1444091796875e-05s
INFO | --- Analysis for culturalinkeddata took 624.5068907737732s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.1622161865234375s
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.29868316650390625s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.021628379821777344s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.528594970703125e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-ares-or took 3.116971254348755s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10991358757019043s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.00083160400390625s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.3206977844238281s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.3392181396484375e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.298324584960938e-06s
INFO | --- Analysis for cz-ares-rzp took 3.3305602073669434s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11295938491821289s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.278933048248291s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.02133345603942871s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.886222839355469e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 9.059906005859375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.2257392406463623s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.1161036491394043s
Availability | VoID file availability check for Integrated pollution registry took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2925996780395508s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020917415618896484s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.838539123535156e-05s
Believability | Calculation of trust value for Integrated pollution registry took 9.059906005859375e-06s
INFO | --- Analysis for cz-cenia-pollution took 3.176255226135254s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.12089014053344727s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.3276982307434082s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.814697265625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 8.821487426757812e-06s
INFO | --- Analysis for cz-contracts took 3.1075899600982666s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.121429443359375s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.3267688751220703s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020760536193847656s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.62396240234375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-bans took 7.4934303760528564s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10869669914245605s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0008714199066162109s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.29605698585510254s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.719329833984375e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-confiscations took 3.0028345584869385s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11687731742858887s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.29990148544311523s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020784854888916016s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.838539123535156e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-focus took 3.1230416297912598s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.11110520362854004s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0009312629699707031s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.3158116340637207s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.02179265022277832s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.3392181396484375e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-inspections took 3.0787851810455322s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.12102746963500977s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0008502006530761719s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.3413505554199219s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.6716461181640625e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-sanctions took 8.819247484207153s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.19561553001403809s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0012273788452148438s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.31540513038635254s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.029273986816406e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 8.58306884765625e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 3.170321226119995s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10667800903320312s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.31240057945251465s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 4.482269287109375e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 8.58306884765625e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 3.0124425888061523s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.7211043834686279s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2931842803955078s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02079176902770996s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.856062650680542s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3400239944458008s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.27628183364868164s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.363059997558594e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.555410623550415s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.35519933700561523s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.001173257827758789s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.2961995601654053s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.021356582641601562s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.553794860839844e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.596128225326538s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3906881809234619s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.3010826110839844s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.522793769836426s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3674609661102295s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.3455202579498291s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.100799560546875e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.584242820739746s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.35765886306762695s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0009109973907470703s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2894706726074219s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02219986915588379s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 4.100799560546875e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-regions took 3.3899784088134766s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.36563706398010254s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.3299446105957031s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 3.933906555175781e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.4451467990875244s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.3689742088317871s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.27275753021240234s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.021875858306884766s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.5508358478546143s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.36208367347717285s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2778193950653076s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.022684812545776367s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.124641418457031e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.5486319065093994s
Availability | SPARQL endpoint availability check for ATC groups took 0.12069964408874512s
Availability | VoID file availability check for ATC groups took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for ATC groups took 0.28222155570983887s
Reputation | Calculation of the PageRank for ATC groups took 0.021041154861450195s
Interlinking | Calculation of Degree of Connection for ATC groups took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ATC groups took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.677078247070312e-05s
Believability | Calculation of trust value for ATC groups took 1.1920928955078125e-05s
INFO | --- Analysis for cz-eh-1-atc took 2.962580442428589s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10476565361022949s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.30057406425476074s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.021303415298461914s
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.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.886222839355469e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 8.106231689453125e-06s
INFO | --- Analysis for cz-fulfillments took 3.0806312561035156s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.047438621520996094s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.296267032623291s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.8160552978515625e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 1.0251998901367188e-05s
INFO | --- Analysis for cz-ic took 3.5075602531433105s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.11517190933227539s
Availability | VoID file availability check for List of Czech data boxes took 0.0005650520324707031s
Extra | Recovery of all triples for List of Czech data boxes took 144.03629970550537s
Performance | Total latancy measurement for List of Czech data boxes took 0.5902044773101807s
Amount of data | Number of triples check for List of Czech data boxes took 9.937892198562622s
Interoperability | New terms check for List of Czech data boxes took 10.802308082580566s
Versatility | Languages check for List of Czech data boxes took 300.1448075771332s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.425330638885498s
Interpretability | RDF structures check for List of Czech data boxes took 0.15220069885253906s
Versatility | Serialization formats check for List of Czech data boxes took 0.17194318771362305s
Availability | RDF dump link check for List of Czech data boxes took 15.286618709564209s
License | MR license check for List of Czech data boxes took 0.42900562286376953s
License | HR license check for List of Czech data boxes took 55.813257455825806s
Amount of data | Number of property check for List of Czech data boxes took 0.13067102432250977s
Understandability | Number of label check for List of Czech data boxes took 1.7140347957611084s
Understandability | URI regex check for List of Czech data boxes took 0.4378013610839844s
Understandability | Vocabs check for List of Czech data boxes took 0.12509846687316895s
Verifiability | Authors check for List of Czech data boxes took 0.13984322547912598s
Verifiability | Publishers check for List of Czech data boxes took 0.12288212776184082s
Performance | Throughput check for List of Czech data boxes took 10.655427932739258s
Amount of data | Check the number of entities for List of Czech data boxes took 3.0682544708251953s
Verifiability | Contribs. check for List of Czech data boxes took 0.14414262771606445s
Interlinking | sameAs chians check for List of Czech data boxes took 0.438579797744751s
Interlinking | skos check for List of Czech data boxes took 0.18738985061645508s
Interlinking | skos check for List of Czech data boxes took 0.10004711151123047s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.24425864219665527s
Currency | Creation date check for List of Czech data boxes took 0.2430744171142578s
Currency | Modification date check for List of Czech data boxes took 0.12408232688903809s
Rep.Conc. | URIs length for List of Czech data boxes took 108.17183828353882s
Interoperability | New vocabularies check for List of Czech data boxes took 10.501855850219727s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.3629436492919922s
Accuracy | Check Functional Property for List of Czech data boxes took 0.2408735752105713s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.2143573760986328s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 30.19022035598755s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.099768877029419s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.574558734893799s
Consistency | Disjoint class check for List of Czech data boxes took 0.11496400833129883s
Consistency | Check Misplaced properties for List of Czech data boxes took 67.35282850265503s
Consistency | Misplaced classes for List of Czech data boxes took 7.5409157276153564s
Consistency | Check Ontology hijacking for List of Czech data boxes took 30.685521125793457s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.3699088096618652s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 61.6426682472229s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.707920551300049s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.3503119945526123s
Security | Sign check for List of Czech data boxes took 0.14284729957580566s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 391.49573493003845s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.7112166881561279s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02305912971496582s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 4.410743713378906e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 9.654048919677734s
Believability | Calculation of trust value for List of Czech data boxes took 8.821487426757812e-06s
INFO | --- Analysis for cz-list-of-databoxes took 1624.3308954238892s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11601543426513672s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005695819854736328s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 140.53469347953796s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6204750537872314s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.678258419036865s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.839231729507446s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1309769153595s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.223541498184204s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1198732852935791s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.20298194885253906s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 16.093764543533325s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1060495376586914s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 54.42705464363098s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11842465400695801s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.7891895771026611s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6199016571044922s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12495636940002441s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12412452697753906s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12055563926696777s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.678696155548096s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.105564594268799s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12021470069885254s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.258098840713501s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10829758644104004s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1076517105102539s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.20796561241149902s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.26901698112487793s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12059307098388672s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 109.46916198730469s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.69729733467102s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.41892337799072266s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12787652015686035s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.19324302673339844s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 32.02949380874634s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.058077096939087s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6608617305755615s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13297677040100098s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 67.91779232025146s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.574446439743042s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 32.163580894470215s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3795230388641357s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 61.5021493434906s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.7414305210113525s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.35617756843566895s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12120699882507324s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 383.78699231147766s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3969125747680664s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.335936069488525s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.298324584960938e-06s
INFO | --- Analysis for cz-nace took 1615.870616197586s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.322706937789917s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006289482116699219s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 431.80021595954895s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.884026050567627s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.49059104919433594s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.5076584815979004s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 300.21938729286194s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.1093666553497314s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0893523693084717s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.140806198120117s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3945882320404053s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8836205005645752s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.5095179080963135s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.18518471717834473s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.072662115097046s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4977595806121826s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.26555752754211426s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4465062618255615s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.25983285903930664s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.65257978439331s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.866455078125e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.20923209190368652s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.22856378555297852s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.5813207626342773s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15537357330322266s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.551490545272827s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.687706708908081s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3857264518737793s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 87.66213178634644s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.17126131057739258s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3543095588684082s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.34334897994995117s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 73.30219769477844s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.4364888668060303s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.695726156234741s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.31218552589416504s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.5951807498931885s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.046033382415771s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 73.40304136276245s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.8086321353912354s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.950918674468994s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.234919548034668s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2969200611114502s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4626321792602539s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 976.9312880039215s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6960504055023193s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.021843910217285156s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.0067901611328125e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0251998901367188e-05s
INFO | --- Analysis for cz-nkod took 24813.369064092636s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.2353687286376953s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.29271554946899414s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.021823644638061523s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007059574127197266s
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 9.059906005859375e-06s
INFO | --- Analysis for cz-orders took 3.172029972076416s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.1799302101135254s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006673336029052734s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 143.74550366401672s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5788488388061523s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.70715069770813s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.743654489517212s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.08866333961487s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.3505465984344482s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.14887452125549316s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.17505764961242676s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 15.263869047164917s
License | MR license check for Institutions of public power of the Czech Republic took 0.6071455478668213s
License | HR license check for Institutions of public power of the Czech Republic took 54.20339512825012s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.12725448608398438s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.699326753616333s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.6247928142547607s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.12363529205322266s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.13378000259399414s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.11389827728271484s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.76811146736145s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.1041359901428223s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.12482714653015137s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.2664504051208496s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.19982290267944336s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.12821507453918457s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.24391937255859375s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.2908506393432617s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.1449127197265625s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 111.466059923172s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 26.67788577079773s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.409501314163208s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.2185220718383789s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.23857331275939941s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 32.22764229774475s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0388541221618652s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.5960981845855713s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.11824321746826172s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 66.95975971221924s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.411714553833008s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 31.456284999847412s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.423607349395752s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 61.43337965011597s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.721580982208252s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.43009281158447266s
Security | Sign check for Institutions of public power of the Czech Republic took 0.17804503440856934s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 389.2399380207062s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.38237881660461426s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021982192993164062s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 6.461143493652344e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 92.5082380771637s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 1.0251998901367188e-05s
INFO | --- Analysis for cz-ovm took 1725.1021656990051s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.11556100845336914s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2828993797302246s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.504753112792969e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-ovm-agendas took 3.0845425128936768s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1425633430480957s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0005717277526855469s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 58.123668909072876s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5466475486755371s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.94147515296936s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 33.50605273246765s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.13404417037964s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13402962684631348s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.4641115665435791s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12989091873168945s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7695956230163574s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11921143531799316s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10508060455322266s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1167905330657959s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.931797981262207s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2388627529144287s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13184237480163574s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20795965194702148s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12575411796569824s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.488062143325806s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.985664367675781e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11528539657592773s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1151723861694336s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13466835021972656s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11387777328491211s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12881946563720703s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.26009607315063477s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11590266227722168s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 222.33700728416443s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16669201850891113s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13469624519348145s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12107372283935547s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.467800855636597s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.219816207885742s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.6035244464874268s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12491464614868164s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 170.1301929950714s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.325400590896606s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.07465171813965s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.3748061656951904s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 171.5477168560028s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.962912082672119s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.26386094093322754s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13010072708129883s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 14.961766719818115s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8639802932739258s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.9073486328125e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-ruian took 1466.4988870620728s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.5192117691040039s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.2786386013031006s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.390975952148438e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 3.897322416305542s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.441913366317749s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.27686071395874023s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.022019624710083008s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.3392181396484375e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.8000969886779785s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.47452878952026367s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.29728150367736816s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0008175373077392578s
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 1.0013580322265625e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 3.80194091796875s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10855436325073242s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0011463165283203125s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.3074805736541748s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.021448612213134766s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.3589859008789062e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.0632669925689697s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.1124274730682373s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.3076488971710205s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02065753936767578s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.075599670410156e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 3.1339967250823975s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.10541343688964844s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.3073441982269287s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.021170616149902344s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-sidc-drugs took 3.1922812461853027s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.2001333236694336s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0013632774353027344s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 146.0783233642578s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5760006904602051s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.616345882415771s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.721256732940674s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1794664859772s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.4657540321350098s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.11085915565490723s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.17992281913757324s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.487774848937988s
License | MR license check for Summary types of Czech institutions of public power took 0.3901505470275879s
License | HR license check for Summary types of Czech institutions of public power took 54.71574640274048s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.12218785285949707s
Understandability | Number of label check for Summary types of Czech institutions of public power took 2.0873329639434814s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.23198962211608887s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.13861703872680664s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.14046072959899902s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.1233527660369873s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.81150197982788s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.0990676879882812s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.11642670631408691s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.30320215225219727s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.17785239219665527s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.12979888916015625s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.2667834758758545s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.25520944595336914s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.11179113388061523s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 110.21507787704468s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 33.701635122299194s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.4333469867706299s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.25646138191223145s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.18660306930541992s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 31.661479234695435s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.065298318862915s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6316635608673096s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.11773300170898438s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 66.88091588020325s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.5351526737213135s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 31.6608784198761s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.4260225296020508s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 61.50973606109619s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.7472286224365234s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.37534117698669434s
Security | Sign check for Summary types of Czech institutions of public power took 0.11328530311584473s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 393.0848491191864s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.6014328002929688s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02185797691345215s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 8.368492126464844e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 29.84700322151184s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.775161743164062e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1673.555097103119s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10068726539611816s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.41182541847229004s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.3855438232421875e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.0922064781188965s
Availability | SPARQL endpoint availability check for State funding providers took 0.10982775688171387s
Availability | VoID file availability check for State funding providers took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for State funding providers took 0.27997875213623047s
Reputation | Calculation of the PageRank for State funding providers took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.814697265625e-05s
Believability | Calculation of trust value for State funding providers took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 2.9778575897216797s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10930085182189941s
Availability | VoID file availability check for Organizations active in R&D took 0.00033211708068847656s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.3022186756134033s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020531415939331055s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.838539123535156e-05s
Believability | Calculation of trust value for Organizations active in R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.1838395595550537s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11151313781738281s
Availability | VoID file availability check for R&D Programmes took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.30154871940612793s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.267692565917969e-05s
Believability | Calculation of trust value for R&D Programmes took 1.049041748046875e-05s
INFO | --- Analysis for cz-vavai-programmes took 3.1124610900878906s
Availability | SPARQL endpoint availability check for R&D Projects took 0.11226582527160645s
Availability | VoID file availability check for R&D Projects took 0.0007874965667724609s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.3405895233154297s
Reputation | Calculation of the PageRank for R&D Projects took 0.02100682258605957s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.1484832763671875e-05s
Believability | Calculation of trust value for R&D Projects took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-projects took 3.161694049835205s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10886430740356445s
Availability | VoID file availability check for Institutional research plans took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.3267066478729248s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.981590270996094e-05s
Believability | Calculation of trust value for Institutional research plans took 1.0013580322265625e-05s
INFO | --- Analysis for cz-vavai-research-plans took 3.1561124324798584s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11277604103088379s
Availability | VoID file availability check for Results of R&D took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.31883883476257324s
Reputation | Calculation of the PageRank for Results of R&D took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.981590270996094e-05s
Believability | Calculation of trust value for Results of R&D took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-results took 3.1479063034057617s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.12041020393371582s
Availability | VoID file availability check for Tenders in R&D took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.27674150466918945s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.022231578826904297s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.1961669921875e-05s
Believability | Calculation of trust value for Tenders in R&D took 9.059906005859375e-06s
INFO | --- Analysis for cz-vavai-tenders took 3.1302247047424316s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 0.0001068115234375s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.29557132720947266s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.0279159545898438e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.239776611328125e-05s
INFO | --- Analysis for czech_addresses took 4.381392240524292s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.6380336284637451s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0007495880126953125s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.26664304733276367s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.021946430206298828s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.383868455886841s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3525431156158447s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.00037169456481933594s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 128.45038318634033s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0343232154846191s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 13.097690105438232s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.128617286682129s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.33142900466919s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.23084282875061035s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.12240743637084961s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.3831357955932617s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.25971484184265137s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2640538215637207s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.2934422492980957s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.33200883865356s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.24438691139221191s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.0761616230010986s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.49036598205566406s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2672841548919678s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.24533557891845703s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.22293686866760254s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.750375747680664s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.700920104980469e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2273707389831543s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.49154114723205566s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.49991679191589355s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.23059535026550293s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.24347257614135742s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.49755287170410156s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.4752695560455322s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 87.83713960647583s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2518434524536133s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3127763271331787s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.2734568119049072s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 44.041460275650024s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2227888107299805s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.620986223220825s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.3023085594177246s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 22.031498908996582s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 7.461344003677368s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 40.48519325256348s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5320768356323242s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 22.912463426589966s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.9425268173217773s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2411355972290039s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.26069211959838867s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 10.269702911376953s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.46654200553894043s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021558761596679688s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00013875961303710938s
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.1444091796875e-05s
INFO | --- Analysis for data-bnf-fr took 823.0778324604034s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.3683617115020752s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.2776367664337158s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.677078247070312e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 8.58306884765625e-06s
INFO | --- Analysis for data-cnr-it took 3.8038787841796875s
Availability | SPARQL endpoint availability check for Data.gov took 1.7621753215789795s
Availability | VoID file availability check for Data.gov took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Data.gov took 0.3018772602081299s
Reputation | Calculation of the PageRank for Data.gov took 0.02285289764404297s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.1948089599609375e-05s
Believability | Calculation of trust value for Data.gov took 8.821487426757812e-06s
INFO | --- Analysis for data-gov took 19.157644987106323s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.03881478309631348s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.3198826313018799s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.021008968353271484s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.43865966796875e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 8.821487426757812e-06s
INFO | --- Analysis for data-gov-ie took 2.929741144180298s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.38690185546875e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.28742361068725586s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020959138870239258s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.104873657226562e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 8.344650268554688e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.780276298522949s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.21476721763611s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.29387497901916504s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020916461944580078s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.127357482910156e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.2874603271484375e-05s
INFO | --- Analysis for data-hnm-hu took 158.52412796020508s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.2174692153930664s
Availability | VoID file availability check for Climb Dataincubator took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2896895408630371s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02128911018371582s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.104873657226562e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.239776611328125e-05s
INFO | --- Analysis for data-incubator-climb took 2.9505507946014404s
Availability | SPARQL endpoint availability check for Discogs in RDF took 9.083747863769531e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.27649736404418945s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020666122436523438s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.298324584960938e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-discogs took 5.002368450164795s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05673480033874512s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.3075871467590332s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.021926164627075195s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 4.9591064453125e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 1.0251998901367188e-05s
INFO | --- Analysis for data-incubator-metoffice took 6.084713459014893s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.06113028526306152s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0003647804260253906s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.29004335403442383s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.463859558105469e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.2636184692382812e-05s
INFO | --- Analysis for data-incubator-moseley took 8.48780632019043s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.07271981239318848s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.3127727508544922s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020610570907592773s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.702278137207031e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.87827205657959s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.7724008560180664s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.30750560760498047s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 0.00010323524475097656s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-nasa took 8.160257339477539s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.05922746658325195s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2780430316925049s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.021607398986816406s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.390975952148438e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.33514404296875e-05s
INFO | --- Analysis for data-incubator-our-airports took 2.798701286315918s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06544351577758789s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2773549556732178s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.751319885253906e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.239776611328125e-05s
INFO | --- Analysis for data-incubator-pokedex took 4.537142038345337s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.06692290306091309s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.3178439140319824s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.021306276321411133s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.678436279296875e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.2636184692382812e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.9315500259399414s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.2957003116607666s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0007817745208740234s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 19.347652673721313s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.6166596412658691s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 20.118746519088745s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5178277492523193s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.173773050308228s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.142528772354126s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.19086384773254395s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.2833445072174072s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.42060256004333496s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.15294337272644043s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.22329473495483398s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.1515154838562s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.8680531978607178s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.155920267105103s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 1.0720553398132324s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.7978205680847168s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.690716028213501s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.539132833480835s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.865070581436157s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.796287536621094e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.15149307250976562s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.6398622989654541s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2886335849761963s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2002544403076172s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.3765397071838379s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.48193931579589844s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.5633025169372559s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 27.672755479812622s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 222.43018054962158s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.17461538314819336s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.1584632396697998s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.11964559555053711s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 12.299299478530884s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.9791243076324463s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.070467710494995s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.18494343757629395s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.5128788948059082s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 7.879733324050903s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 7.992910385131836s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.5059092044830322s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.6856293678283691s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.9457571506500244s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.36847352981567383s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.13768792152404785s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.10915446281433105s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.390303373336792s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.152557373046875e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 255.24088263511658s
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 955.2694659233093s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8387167453765869s
Availability | VoID file availability check for Persée in RDF took 0.00047588348388671875s
Extra | Recovery of all triples for Persée in RDF took 1.0521924495697021s
Performance | Total latancy measurement for Persée in RDF took 0.6572275161743164s
Amount of data | Number of triples check for Persée in RDF took 0.9347882270812988s
Interoperability | New terms check for Persée in RDF took 1.9098045825958252s
Versatility | Languages check for Persée in RDF took 121.21976661682129s
Interpretability | Number of blank nodes check for Persée in RDF took 0.5649869441986084s
Interpretability | RDF structures check for Persée in RDF took 1.3807108402252197s
Versatility | Serialization formats check for Persée in RDF took 1.1202027797698975s
Availability | RDF dump link check for Persée in RDF took 0.3406052589416504s
License | MR license check for Persée in RDF took 2.1178641319274902s
License | HR license check for Persée in RDF took 41.2883996963501s
Amount of data | Number of property check for Persée in RDF took 0.1289219856262207s
Understandability | Number of label check for Persée in RDF took 3.4563498497009277s
Understandability | URI regex check for Persée in RDF took 1.0720946788787842s
Understandability | Vocabs check for Persée in RDF took 0.48905253410339355s
Verifiability | Authors check for Persée in RDF took 0.5753295421600342s
Verifiability | Publishers check for Persée in RDF took 0.34151339530944824s
Performance | Throughput check for Persée in RDF took 10.59203314781189s
Amount of data | Check the number of entities for Persée in RDF took 8.440017700195312e-05s
Verifiability | Contribs. check for Persée in RDF took 0.319263219833374s
Interlinking | sameAs chians check for Persée in RDF took 0.26026487350463867s
Interlinking | skos check for Persée in RDF took 0.8502981662750244s
Interlinking | skos check for Persée in RDF took 0.1317272186279297s
Timeliness | dataset update frequency check for Persée in RDF took 0.7906606197357178s
Currency | Creation date check for Persée in RDF took 0.6714019775390625s
Currency | Modification date check for Persée in RDF took 1.0644330978393555s
Rep.Conc. | URIs length for Persée in RDF took 3.469481945037842s
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.1295640468597412s
Accuracy | Check Functional Property for Persée in RDF took 0.1535041332244873s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.1487267017364502s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.6491611003875732s
Accuracy | Check White space in annotation for Persée in RDF took 0.039388418197631836s
Accuracy | Check Datatype consistency for Persée in RDF took 0.02742290496826172s
Consistency | Disjoint class check for Persée in RDF took 0.34048986434936523s
Consistency | Check Misplaced properties for Persée in RDF took 2.5897161960601807s
Consistency | Misplaced classes for Persée in RDF took 0.22137713432312012s
Consistency | Check Ontology hijacking for Persée in RDF took 1.9441237449645996s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.3356566429138184s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.8414666652679443s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03174328804016113s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.14490866661071777s
Security | Sign check for Persée in RDF took 0.8188707828521729s
Availability | Check URIs Dereferenciability for Persée in RDF took 1393.3879628181458s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.6291368007659912s
Reputation | Calculation of the PageRank for Persée in RDF took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 7.605552673339844e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.430511474609375e-06s
Believability | Calculation of trust value for Persée in RDF took 1.33514404296875e-05s
INFO | --- Analysis for data-persee-fr took 1643.6082317829132s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.4990670680999756s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.3339109420776367s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.021900415420532227s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.0001220703125s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.1205673217773438e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.66730260848999s
Availability | SPARQL endpoint availability check for Open Data Web took 10.574889659881592s
Availability | VoID file availability check for Open Data Web took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.284191370010376s
Reputation | Calculation of the PageRank for Open Data Web took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.3855438232421875e-05s
Believability | Calculation of trust value for Open Data Web took 1.239776611328125e-05s
INFO | --- Analysis for data.odw.tw took 18.31858730316162s
Availability | SPARQL endpoint availability check for datahub took 5.412101745605469e-05s
Availability | VoID file availability check for datahub took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for datahub took 0.29016923904418945s
Reputation | Calculation of the PageRank for datahub took 0.021118879318237305s
Interlinking | Calculation of Degree of Connection for datahub took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for datahub took 4.8160552978515625e-05s
Believability | Calculation of trust value for datahub took 1.3113021850585938e-05s
INFO | --- Analysis for datahub took 4.384962320327759s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.814646005630493s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.31644606590270996s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.170967102050781e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 6.67572021484375e-06s
INFO | --- Analysis for datahub-kr-datamap took 13.348480224609375s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3519001007080078s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3051588535308838s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.343292236328125e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.2874603271484375e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.45730185508728s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.28041172027588s
Availability | VoID file availability check for datos-artium-org took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.3068685531616211s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011539459228515625s
Believability | Calculation of trust value for datos-artium-org took 1.33514404296875e-05s
INFO | --- Analysis for datos-artium-org took 164.99878025054932s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8617660999298096s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006799697875976562s
Extra | Recovery of all triples for Datos.bcn.cl took 47.454442262649536s
Performance | Total latancy measurement for Datos.bcn.cl took 6.100003719329834s
Amount of data | Number of triples check for Datos.bcn.cl took 5.0353288650512695s
Interoperability | New terms check for Datos.bcn.cl took 3.835709571838379s
Versatility | Languages check for Datos.bcn.cl took 301.0600905418396s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.267327070236206s
Security | Check HTTPS for Datos.bcn.cl took 0.7303121089935303s
Interpretability | RDF structures check for Datos.bcn.cl took 1.3373730182647705s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2927184104919434s
Availability | RDF dump link check for Datos.bcn.cl took 1.2607393264770508s
License | MR license check for Datos.bcn.cl took 1.235002040863037s
License | HR license check for Datos.bcn.cl took 33.67906069755554s
Amount of data | Number of property check for Datos.bcn.cl took 1.2636046409606934s
Understandability | Number of label check for Datos.bcn.cl took 1.4527208805084229s
Understandability | URI regex check for Datos.bcn.cl took 2.496049165725708s
Understandability | Vocabs check for Datos.bcn.cl took 1.21348237991333s
Verifiability | Authors check for Datos.bcn.cl took 1.2794408798217773s
Verifiability | Publishers check for Datos.bcn.cl took 1.2456974983215332s
Performance | Throughput check for Datos.bcn.cl took 12.74612832069397s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.128715515136719e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2408545017242432s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2454004287719727s
Interlinking | skos check for Datos.bcn.cl took 1.2307336330413818s
Interlinking | skos check for Datos.bcn.cl took 1.230125904083252s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.260714054107666s
Currency | Creation date check for Datos.bcn.cl took 2.4771556854248047s
Currency | Modification date check for Datos.bcn.cl took 1.2643344402313232s
Rep.Conc. | URIs length for Datos.bcn.cl took 48.14777135848999s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2510466575622559s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.240736961364746s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.2476296424865723s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 52.91602659225464s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.32065677642822266s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2699120044708252s
Consistency | Disjoint class check for Datos.bcn.cl took 1.2250428199768066s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.617663860321045s
Consistency | Misplaced classes for Datos.bcn.cl took 2.070636510848999s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 18.965282678604126s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3658905029296875s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.599292039871216s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.30326080322265625s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.5094072818756104s
Security | Sign check for Datos.bcn.cl took 1.2423865795135498s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7919.575326919556s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.7223446369171143s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.024521827697753906s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 7.677078247070312e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.915496826171875e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.9073486328125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 9.298324584960938e-06s
INFO | --- Analysis for datos-bcn-cl took 8816.706530094147s
Availability | SPARQL endpoint availability check for datos.bne.es took 2.8003857135772705s
Availability | VoID file availability check for datos.bne.es took 0.000728607177734375s
Extra | Recovery of all triples for datos.bne.es took 138.34996819496155s
Performance | Total latancy measurement for datos.bne.es took 4.787140369415283s
Amount of data | Number of triples check for datos.bne.es took 2.708759069442749s
Interoperability | New terms check for datos.bne.es took 2.3491756916046143s
Versatility | Languages check for datos.bne.es took 61.46977758407593s
Interpretability | Number of blank nodes check for datos.bne.es took 0.317960262298584s
Security | Check HTTPS for datos.bne.es took 0.18289422988891602s
Interpretability | RDF structures check for datos.bne.es took 0.6162714958190918s
Versatility | Serialization formats check for datos.bne.es took 2.3822579383850098s
Availability | RDF dump link check for datos.bne.es took 0.3772873878479004s
License | MR license check for datos.bne.es took 1.2899343967437744s
License | HR license check for datos.bne.es took 62.26682639122009s
Amount of data | Number of property check for datos.bne.es took 0.321505069732666s
Understandability | Number of label check for datos.bne.es took 3.2257368564605713s
Understandability | URI regex check for datos.bne.es took 2.923884391784668s
Understandability | Vocabs check for datos.bne.es took 0.40903782844543457s
Verifiability | Authors check for datos.bne.es took 2.2309224605560303s
Verifiability | Publishers check for datos.bne.es took 0.38924074172973633s
Performance | Throughput check for datos.bne.es took 21.1596462726593s
Amount of data | Check the number of entities for datos.bne.es took 7.581710815429688e-05s
Verifiability | Contribs. check for datos.bne.es took 2.282097816467285s
Interlinking | sameAs chians check for datos.bne.es took 2.3620123863220215s
Interlinking | skos check for datos.bne.es took 2.4876086711883545s
Interlinking | skos check for datos.bne.es took 0.25309133529663086s
Timeliness | dataset update frequency check for datos.bne.es took 2.2289769649505615s
Currency | Creation date check for datos.bne.es took 2.5824615955352783s
Currency | Modification date check for datos.bne.es took 4.54363226890564s
Rep.Conc. | URIs length for datos.bne.es took 53.28428339958191s
Interoperability | New vocabularies check for datos.bne.es took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.559154748916626s
Accuracy | Check Functional Property for datos.bne.es took 2.0910558700561523s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.30271434783935547s
Accuracy | Check Empty annotation labels for datos.bne.es took 43.240156412124634s
Accuracy | Check White space in annotation for datos.bne.es took 1.603461503982544s
Accuracy | Check Datatype consistency for datos.bne.es took 1.3259620666503906s
Consistency | Disjoint class check for datos.bne.es took 0.3355083465576172s
Consistency | Check Misplaced properties for datos.bne.es took 11.3144371509552s
Consistency | Misplaced classes for datos.bne.es took 4.3438560962677s
Consistency | Check Ontology hijacking for datos.bne.es took 42.760796785354614s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.318375825881958s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 12.101614236831665s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.4112632274627686s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.2972218990325928s
Security | Sign check for datos.bne.es took 3.0962095260620117s
Availability | Check URIs Dereferenciability for datos.bne.es took 10.30888032913208s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.4198331832885742s
Reputation | Calculation of the PageRank for datos.bne.es took 0.021329402923583984s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00012087821960449219s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 2.384185791015625e-06s
Believability | Calculation of trust value for datos.bne.es took 1.2636184692382812e-05s
INFO | --- Analysis for datos-bne-es took 638.9345881938934s
Availability | SPARQL endpoint availability check for dbacademic took 0.057656288146972656s
Availability | VoID file availability check for dbacademic took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for dbacademic took 0.2853434085845947s
Reputation | Calculation of the PageRank for dbacademic took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.218650817871094e-05s
Believability | Calculation of trust value for dbacademic took 9.5367431640625e-06s
INFO | --- Analysis for dbacademic took 2.7435414791107178s
Availability | SPARQL endpoint availability check for DBkWik took 0.3569958209991455s
Availability | VoID file availability check for DBkWik took 0.0011839866638183594s
Extra | Recovery of all triples for DBkWik took 1.532278299331665s
Performance | Total latancy measurement for DBkWik took 0.4260835647583008s
Amount of data | Number of triples check for DBkWik took 5.580618858337402s
Interoperability | New terms check for DBkWik took 2.0771915912628174s
Versatility | Languages check for DBkWik took 60.20496964454651s
Interpretability | Number of blank nodes check for DBkWik took 0.23858213424682617s
Interpretability | RDF structures check for DBkWik took 0.21204519271850586s
Versatility | Serialization formats check for DBkWik took 0.45509886741638184s
Availability | RDF dump link check for DBkWik took 2.692946434020996s
License | MR license check for DBkWik took 0.24216008186340332s
License | HR license check for DBkWik took 60.99349546432495s
Amount of data | Number of property check for DBkWik took 0.13075804710388184s
Understandability | Number of label check for DBkWik took 2.2681150436401367s
Understandability | URI regex check for DBkWik took 0.3021817207336426s
Understandability | Vocabs check for DBkWik took 0.12415313720703125s
Verifiability | Authors check for DBkWik took 0.11490869522094727s
Verifiability | Publishers check for DBkWik took 0.08760452270507812s
Performance | Throughput check for DBkWik took 10.529103755950928s
Amount of data | Check the number of entities for DBkWik took 8.273124694824219e-05s
Verifiability | Contribs. check for DBkWik took 0.11005568504333496s
Interlinking | sameAs chians check for DBkWik took 0.27457237243652344s
Interlinking | skos check for DBkWik took 0.28990888595581055s
Interlinking | skos check for DBkWik took 0.08389663696289062s
Timeliness | dataset update frequency check for DBkWik took 0.1537182331085205s
Currency | Creation date check for DBkWik took 0.35242390632629395s
Currency | Modification date check for DBkWik took 0.1996626853942871s
Rep.Conc. | URIs length for DBkWik took 11.20193862915039s
Interoperability | New vocabularies check for DBkWik took 7.393672227859497s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.10927295684814453s
Accuracy | Check Functional Property for DBkWik took 0.22322726249694824s
Accuracy | Check Inverse Functional Property for DBkWik took 0.18863797187805176s
Accuracy | Check Empty annotation labels for DBkWik took 0.5195209980010986s
Accuracy | Check White space in annotation for DBkWik took 0.023610591888427734s
Accuracy | Check Datatype consistency for DBkWik took 0.03750038146972656s
Consistency | Disjoint class check for DBkWik took 0.1103048324584961s
Consistency | Check Misplaced properties for DBkWik took 12.047594785690308s
Consistency | Misplaced classes for DBkWik took 0.6058285236358643s
Consistency | Check Ontology hijacking for DBkWik took 2.098144292831421s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.2855720520019531s
Consistency | Check Invalid usage of undefined properties for DBkWik took 12.89521336555481s
Conciseness | Check Extensional conciseness for DBkWik took 0.03365826606750488s
Conciseness | Check Intensional conciseness for DBkWik took 1.0157630443572998s
Security | Sign check for DBkWik took 0.3247978687286377s
Availability | Check URIs Dereferenciability for DBkWik took 10.127080202102661s
Completeness | Calculation of interlinking completeness for DBkWik took 0.41733694076538086s
Reputation | Calculation of the PageRank for DBkWik took 0.021201610565185547s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 2.045478105545044s
Believability | Calculation of trust value for DBkWik took 1.2159347534179688e-05s
INFO | --- Analysis for dbkwik took 1274.4331352710724s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 9.34600830078125e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.3144264221191406s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.02118706703186035s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011754035949707031s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.33514404296875e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 4.59648323059082s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.454395055770874s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005939006805419922s
Extra | Recovery of all triples for dblp Knowledge Graph took 7.617917060852051s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.8173418045043945s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.1647968292236328s
Interoperability | New terms check for dblp Knowledge Graph took 1.834369421005249s
Versatility | Languages check for dblp Knowledge Graph took 0.20035505294799805s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 3.6973776817321777s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1805112361907959s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.18132448196411133s
Availability | RDF dump link check for dblp Knowledge Graph took 0.15081143379211426s
License | MR license check for dblp Knowledge Graph took 0.1769545078277588s
License | HR license check for dblp Knowledge Graph took 30.17080044746399s
Amount of data | Number of property check for dblp Knowledge Graph took 0.14868545532226562s
Understandability | Number of label check for dblp Knowledge Graph took 0.4296541213989258s
Understandability | URI regex check for dblp Knowledge Graph took 0.3043398857116699s
Understandability | Vocabs check for dblp Knowledge Graph took 0.16411304473876953s
Verifiability | Authors check for dblp Knowledge Graph took 0.1503443717956543s
Verifiability | Publishers check for dblp Knowledge Graph took 0.1887063980102539s
Performance | Throughput check for dblp Knowledge Graph took 10.874146223068237s
Amount of data | Check the number of entities for dblp Knowledge Graph took 8.893013000488281e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.15739202499389648s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.19192743301391602s
Interlinking | skos check for dblp Knowledge Graph took 0.13797736167907715s
Interlinking | skos check for dblp Knowledge Graph took 0.15536880493164062s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.17612147331237793s
Currency | Creation date check for dblp Knowledge Graph took 0.3093125820159912s
Currency | Modification date check for dblp Knowledge Graph took 0.30300164222717285s
Rep.Conc. | URIs length for dblp Knowledge Graph took 15.17543649673462s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.1547379493713379s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.1286923885345459s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.12712717056274414s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 6.86142897605896s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.084501028060913s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.0471508502960205s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.1691608428955078s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.2973966598510742s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 5.4456140995025635s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 17587.652713298798s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 5.213908910751343s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.754007339477539s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.17401790618896484s
Security | Sign check for dblp Knowledge Graph took 0.1656179428100586s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 3.417264223098755s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.904425859451294s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.8596649169921875e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for dblp-kg took 17750.39435648918s
Availability | SPARQL endpoint availability check for DBnary took 0.2848649024963379s
Availability | VoID file availability check for DBnary took 0.0005762577056884766s
Extra | Recovery of all triples for DBnary took 1.1564810276031494s
Performance | Total latancy measurement for DBnary took 0.4153428077697754s
Amount of data | Number of triples check for DBnary took 1.2591581344604492s
Interoperability | New terms check for DBnary took 3.6548726558685303s
Versatility | Languages check for DBnary took 60.721205949783325s
Interpretability | Number of blank nodes check for DBnary took 4.013124465942383s
Security | Check HTTPS for DBnary took 0.20492029190063477s
Interpretability | RDF structures check for DBnary took 0.33582019805908203s
Versatility | Serialization formats check for DBnary took 0.44676828384399414s
Availability | RDF dump link check for DBnary took 0.2125999927520752s
License | MR license check for DBnary took 0.8746693134307861s
License | HR license check for DBnary took 61.04909157752991s
Amount of data | Number of property check for DBnary took 0.09539604187011719s
Understandability | Number of label check for DBnary took 0.9694247245788574s
Understandability | URI regex check for DBnary took 0.16278314590454102s
Understandability | Vocabs check for DBnary took 0.1244652271270752s
Verifiability | Authors check for DBnary took 0.18080663681030273s
Verifiability | Publishers check for DBnary took 0.19037747383117676s
Performance | Throughput check for DBnary took 10.359002828598022s
Amount of data | Check the number of entities for DBnary took 7.62939453125e-05s
Verifiability | Contribs. check for DBnary took 0.1578211784362793s
Interlinking | sameAs chians check for DBnary took 0.09458041191101074s
Interlinking | skos check for DBnary took 0.15561747550964355s
Interlinking | skos check for DBnary took 0.07076883316040039s
Timeliness | dataset update frequency check for DBnary took 0.15746855735778809s
Currency | Creation date check for DBnary took 0.2607462406158447s
Currency | Modification date check for DBnary took 0.22240543365478516s
Rep.Conc. | URIs length for DBnary took 11.145511150360107s
Interoperability | New vocabularies check for DBnary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.08811068534851074s
Accuracy | Check Functional Property for DBnary took 0.1460883617401123s
Accuracy | Check Inverse Functional Property for DBnary took 0.12682318687438965s
Accuracy | Check Empty annotation labels for DBnary took 0.41188859939575195s
Accuracy | Check White space in annotation for DBnary took 0.030904769897460938s
Accuracy | Check Datatype consistency for DBnary took 0.02837228775024414s
Consistency | Disjoint class check for DBnary took 0.15593910217285156s
Consistency | Check Misplaced properties for DBnary took 8.65979290008545s
Consistency | Misplaced classes for DBnary took 0.24114108085632324s
Consistency | Check Ontology hijacking for DBnary took 1.7800555229187012s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.395188570022583s
Consistency | Check Invalid usage of undefined properties for DBnary took 9.838285207748413s
Conciseness | Check Extensional conciseness for DBnary took 0.03887677192687988s
Conciseness | Check Intensional conciseness for DBnary took 0.17637419700622559s
Security | Sign check for DBnary took 0.08977150917053223s
Availability | Check URIs Dereferenciability for DBnary took 10.75223684310913s
Completeness | Calculation of interlinking completeness for DBnary took 0.30292391777038574s
Reputation | Calculation of the PageRank for DBnary took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for DBnary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBnary took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for DBnary took 5.1975250244140625e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.430511474609375e-06s
Believability | Calculation of trust value for DBnary took 1.2874603271484375e-05s
INFO | --- Analysis for dbnary took 297.6847114562988s
Availability | SPARQL endpoint availability check for DBpedia took 31.078205823898315s
Availability | VoID file availability check for DBpedia took 0.0008177757263183594s
Extra | Recovery of all triples for DBpedia took 44.98599028587341s
Performance | Total latancy measurement for DBpedia took 10.427456378936768s
Amount of data | Number of triples check for DBpedia took 1.6040902137756348s
Interoperability | New terms check for DBpedia took 5.764930248260498s
Versatility | Languages check for DBpedia took 32.684813261032104s
Interpretability | Number of blank nodes check for DBpedia took 0.9864823818206787s
Security | Check HTTPS for DBpedia took 0.327603816986084s
Interpretability | RDF structures check for DBpedia took 1.131622314453125s
Versatility | Serialization formats check for DBpedia took 0.7552721500396729s
Availability | RDF dump link check for DBpedia took 0.6036689281463623s
License | MR license check for DBpedia took 5.943958044052124s
License | HR license check for DBpedia took 42.953277826309204s
Amount of data | Number of property check for DBpedia took 0.5888800621032715s
Understandability | Number of label check for DBpedia took 6.4394690990448s
Understandability | URI regex check for DBpedia took 1.1883158683776855s
Understandability | Vocabs check for DBpedia took 0.7401278018951416s
Verifiability | Authors check for DBpedia took 0.6004257202148438s
Verifiability | Publishers check for DBpedia took 0.5782985687255859s
Performance | Throughput check for DBpedia took 18.030044555664062s
Amount of data | Check the number of entities for DBpedia took 8.273124694824219e-05s
Verifiability | Contribs. check for DBpedia took 0.5786440372467041s
Interlinking | sameAs chians check for DBpedia took 3.305751323699951s
Interlinking | skos check for DBpedia took 1.2808899879455566s
Interlinking | skos check for DBpedia took 0.5541379451751709s
Timeliness | dataset update frequency check for DBpedia took 0.8857612609863281s
Currency | Creation date check for DBpedia took 1.2917115688323975s
Currency | Modification date check for DBpedia took 2.795167922973633s
Rep.Conc. | URIs length for DBpedia took 46.468424558639526s
Interoperability | New vocabularies check for DBpedia took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.5969042778015137s
Accuracy | Check Functional Property for DBpedia took 0.5537407398223877s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5911662578582764s
Accuracy | Check Empty annotation labels for DBpedia took 2.5170581340789795s
Accuracy | Check White space in annotation for DBpedia took 0.029782533645629883s
Accuracy | Check Datatype consistency for DBpedia took 0.027530193328857422s
Consistency | Disjoint class check for DBpedia took 0.6307544708251953s
Consistency | Check Misplaced properties for DBpedia took 35.12368392944336s
Consistency | Misplaced classes for DBpedia took 42.17848515510559s
Consistency | Check Ontology hijacking for DBpedia took 66.26249384880066s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2356386184692383s
Consistency | Check Invalid usage of undefined properties for DBpedia took 10.335468292236328s
Conciseness | Check Extensional conciseness for DBpedia took 0.03296852111816406s
Conciseness | Check Intensional conciseness for DBpedia took 30.540786743164062s
Security | Sign check for DBpedia took 0.592388391494751s
Availability | Check URIs Dereferenciability for DBpedia took 8416.68297123909s
Completeness | Calculation of interlinking completeness for DBpedia took 0.776317834854126s
Reputation | Calculation of the PageRank for DBpedia took 0.02130866050720215s
Interlinking | Calculation of Degree of Connection for DBpedia took 6.270408630371094e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009343624114990234s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia took 12630.147206306458s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.482269287109375e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.3642158508300781s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.009506225585938e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.1920928955078125e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 8.082788228988647s
Availability | SPARQL endpoint availability check for DBpedia Commons took 3.8609516620635986s
Availability | VoID file availability check for DBpedia Commons took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.33959436416625977s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.985664367675781e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.2874603271484375e-05s
INFO | --- Analysis for dbpedia-commons took 14.43828797340393s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.39730167388916016s
Availability | VoID file availability check for DBpedia in Greek took 0.0006763935089111328s
Extra | Recovery of all triples for DBpedia in Greek took 1.175908088684082s
Performance | Total latancy measurement for DBpedia in Greek took 1.1870436668395996s
Amount of data | Number of triples check for DBpedia in Greek took 0.29148077964782715s
Interoperability | New terms check for DBpedia in Greek took 1.7016491889953613s
Versatility | Languages check for DBpedia in Greek took 14.3942289352417s
Interpretability | Number of blank nodes check for DBpedia in Greek took 0.24833464622497559s
Security | Check HTTPS for DBpedia in Greek took 0.14327597618103027s
Interpretability | RDF structures check for DBpedia in Greek took 0.2897520065307617s
Versatility | Serialization formats check for DBpedia in Greek took 0.27774715423583984s
Availability | RDF dump link check for DBpedia in Greek took 0.24951910972595215s
License | MR license check for DBpedia in Greek took 0.30405473709106445s
License | HR license check for DBpedia in Greek took 3.502429246902466s
Amount of data | Number of property check for DBpedia in Greek took 0.23727893829345703s
Understandability | Number of label check for DBpedia in Greek took 0.3962686061859131s
Understandability | URI regex check for DBpedia in Greek took 0.5081133842468262s
Understandability | Vocabs check for DBpedia in Greek took 0.24814844131469727s
Verifiability | Authors check for DBpedia in Greek took 0.25565457344055176s
Verifiability | Publishers check for DBpedia in Greek took 0.25194764137268066s
Performance | Throughput check for DBpedia in Greek took 11.833046436309814s
Amount of data | Check the number of entities for DBpedia in Greek took 7.128715515136719e-05s
Verifiability | Contribs. check for DBpedia in Greek took 0.3164985179901123s
Interlinking | sameAs chians check for DBpedia in Greek took 0.3198995590209961s
Interlinking | skos check for DBpedia in Greek took 0.5313022136688232s
Interlinking | skos check for DBpedia in Greek took 0.22024965286254883s
Timeliness | dataset update frequency check for DBpedia in Greek took 0.3588893413543701s
Currency | Creation date check for DBpedia in Greek took 0.47678518295288086s
Currency | Modification date check for DBpedia in Greek took 0.4747586250305176s
Rep.Conc. | URIs length for DBpedia in Greek took 1.3147459030151367s
Interoperability | New vocabularies check for DBpedia in Greek took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Greek took 0.24524784088134766s
Accuracy | Check Functional Property for DBpedia in Greek took 0.28430652618408203s
Accuracy | Check Inverse Functional Property for DBpedia in Greek took 0.2550961971282959s
Consistency | Disjoint class check for DBpedia in Greek took 0.24466562271118164s
Consistency | Check Misplaced properties for DBpedia in Greek took 1.1099002361297607s
Consistency | Check Ontology hijacking for DBpedia in Greek took 0.4709358215332031s
Consistency | Check Invalid usage of undefined properties for DBpedia in Greek took 2.0343430042266846s
Conciseness | Check Extensional conciseness for DBpedia in Greek took 0.0001862049102783203s
Security | Sign check for DBpedia in Greek took 0.2666144371032715s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.37340784072875977s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.021389245986938477s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0009291172027587891s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00024080276489257812s
Interoperability | Check the re-using of existing vocabs for DBpedia in Greek took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Greek took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-el took 125.77618861198425s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.45082831382751465s
Availability | VoID file availability check for DBpedia in Spanish took 0.0005536079406738281s
Extra | Recovery of all triples for DBpedia in Spanish took 3.076580286026001s
Performance | Total latancy measurement for DBpedia in Spanish took 1.2014870643615723s
Amount of data | Number of triples check for DBpedia in Spanish took 0.9355993270874023s
Interoperability | New terms check for DBpedia in Spanish took 2.8414294719696045s
Versatility | Languages check for DBpedia in Spanish took 60.69254398345947s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.46961188316345215s
Security | Check HTTPS for DBpedia in Spanish took 0.1282975673675537s
Interpretability | RDF structures check for DBpedia in Spanish took 0.9828884601593018s
Versatility | Serialization formats check for DBpedia in Spanish took 0.4944782257080078s
Availability | RDF dump link check for DBpedia in Spanish took 0.354278564453125s
License | MR license check for DBpedia in Spanish took 0.6732416152954102s
License | HR license check for DBpedia in Spanish took 60.431641817092896s
Amount of data | Number of property check for DBpedia in Spanish took 0.3369159698486328s
Understandability | Number of label check for DBpedia in Spanish took 1.6507909297943115s
Understandability | URI regex check for DBpedia in Spanish took 0.749321699142456s
Understandability | Vocabs check for DBpedia in Spanish took 0.4862179756164551s
Verifiability | Authors check for DBpedia in Spanish took 0.29501891136169434s
Verifiability | Publishers check for DBpedia in Spanish took 0.29624223709106445s
Performance | Throughput check for DBpedia in Spanish took 11.418874979019165s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.581710815429688e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.31022191047668457s
Interlinking | sameAs chians check for DBpedia in Spanish took 1.1357145309448242s
Interlinking | skos check for DBpedia in Spanish took 0.5783402919769287s
Interlinking | skos check for DBpedia in Spanish took 0.25019097328186035s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.41434693336486816s
Currency | Creation date check for DBpedia in Spanish took 0.6105697154998779s
Currency | Modification date check for DBpedia in Spanish took 0.5987370014190674s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.931583642959595s
Interoperability | New vocabularies check for DBpedia in Spanish took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.3162117004394531s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.4341404438018799s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.548133134841919s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.0786371231079102s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.03061223030090332s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.0331721305847168s
Consistency | Disjoint class check for DBpedia in Spanish took 0.2963378429412842s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.262984991073608s
Consistency | Misplaced classes for DBpedia in Spanish took 1.1230409145355225s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.350515604019165s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.2690551280975342s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.865031480789185s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03287363052368164s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.4195377826690674s
Security | Sign check for DBpedia in Spanish took 0.3207669258117676s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 3.3266005516052246s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.4649181365966797s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.022238492965698242s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011134147644042969s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 2.1457672119140625e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-es took 1720.575347185135s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.1769137382507324s
Availability | VoID file availability check for DBpedia in Basque took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.33055686950683594s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02138519287109375s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 3.123283386230469e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.457069396972656e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-eu took 7.47932505607605s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.1386709213256836s
Availability | VoID file availability check for DBpedia in French took 0.00058746337890625s
Extra | Recovery of all triples for DBpedia in French took 83.02468729019165s
Performance | Total latancy measurement for DBpedia in French took 0.5057437419891357s
Amount of data | Number of triples check for DBpedia in French took 3.3530046939849854s
Interoperability | New terms check for DBpedia in French took 2.3612682819366455s
Versatility | Languages check for DBpedia in French took 300.09034180641174s
Interpretability | Number of blank nodes check for DBpedia in French took 0.6246671676635742s
Security | Check HTTPS for DBpedia in French took 0.21342086791992188s
Interpretability | RDF structures check for DBpedia in French took 0.4496173858642578s
Versatility | Serialization formats check for DBpedia in French took 0.30056047439575195s
Availability | RDF dump link check for DBpedia in French took 7.124065160751343s
License | MR license check for DBpedia in French took 1.4835176467895508s
License | HR license check for DBpedia in French took 206.4690854549408s
Amount of data | Number of property check for DBpedia in French took 0.23898983001708984s
Understandability | Number of label check for DBpedia in French took 1.648346185684204s
Understandability | URI regex check for DBpedia in French took 0.26786279678344727s
Understandability | Vocabs check for DBpedia in French took 0.15934205055236816s
Verifiability | Authors check for DBpedia in French took 0.20506000518798828s
Verifiability | Publishers check for DBpedia in French took 0.1334395408630371s
Performance | Throughput check for DBpedia in French took 10.575261116027832s
Amount of data | Check the number of entities for DBpedia in French took 2.1245596408843994s
Verifiability | Contribs. check for DBpedia in French took 0.14702343940734863s
Interlinking | sameAs chians check for DBpedia in French took 0.44979095458984375s
Interlinking | skos check for DBpedia in French took 0.2694721221923828s
Interlinking | skos check for DBpedia in French took 0.08016681671142578s
Timeliness | dataset update frequency check for DBpedia in French took 0.2097303867340088s
Currency | Creation date check for DBpedia in French took 0.3189053535461426s
Currency | Modification date check for DBpedia in French took 0.20982980728149414s
Rep.Conc. | URIs length for DBpedia in French took 38.49328112602234s
Interoperability | New vocabularies check for DBpedia in French took 8.849879264831543s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.11142587661743164s
Accuracy | Check Functional Property for DBpedia in French took 0.10961794853210449s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.0892496109008789s
Accuracy | Check Empty annotation labels for DBpedia in French took 22.921315670013428s
Accuracy | Check White space in annotation for DBpedia in French took 3.082878351211548s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6313846111297607s
Consistency | Disjoint class check for DBpedia in French took 0.1807551383972168s
Consistency | Check Misplaced properties for DBpedia in French took 7.125629663467407s
Consistency | Misplaced classes for DBpedia in French took 9.001398801803589s
Consistency | Check Ontology hijacking for DBpedia in French took 23.239603281021118s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.3924291133880615s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.989405155181885s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.0865540504455566s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.6029250621795654s
Security | Sign check for DBpedia in French took 0.10991597175598145s
Availability | Check URIs Dereferenciability for DBpedia in French took 2129.894305706024s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7869524955749512s
Reputation | Calculation of the PageRank for DBpedia in French took 0.022588729858398438s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 6.628036499023438e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00010037422180175781s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 6.8907153606414795s
Believability | Calculation of trust value for DBpedia in French took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-fr took 3484.829631090164s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.937258005142212s
Availability | VoID file availability check for DBpedia in Japanese took 4.071755886077881s
Extra | Recovery of all triples for DBpedia in Japanese took 5.463200569152832s
Performance | Total latancy measurement for DBpedia in Japanese took 6.692511796951294s
Amount of data | Number of triples check for DBpedia in Japanese took 32.90841865539551s
Interoperability | New terms check for DBpedia in Japanese took 17.709522247314453s
Versatility | Languages check for DBpedia in Japanese took 1.3295722007751465s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3427517414093018s
Security | Check HTTPS for DBpedia in Japanese took 0.8120894432067871s
Interpretability | RDF structures check for DBpedia in Japanese took 1.383117914199829s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3687984943389893s
Availability | RDF dump link check for DBpedia in Japanese took 1.3164825439453125s
License | MR license check for DBpedia in Japanese took 1.3677759170532227s
License | HR license check for DBpedia in Japanese took 92.78953218460083s
Amount of data | Number of property check for DBpedia in Japanese took 1.3295133113861084s
Understandability | Number of label check for DBpedia in Japanese took 8.641629695892334s
Understandability | URI regex check for DBpedia in Japanese took 2.68412446975708s
Understandability | Vocabs check for DBpedia in Japanese took 1.3219094276428223s
Verifiability | Authors check for DBpedia in Japanese took 1.3478021621704102s
Verifiability | Publishers check for DBpedia in Japanese took 1.3387935161590576s
Performance | Throughput check for DBpedia in Japanese took 13.268102645874023s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.486343383789062e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3332710266113281s
Interlinking | sameAs chians check for DBpedia in Japanese took 3.13718581199646s
Interlinking | skos check for DBpedia in Japanese took 1.3549094200134277s
Interlinking | skos check for DBpedia in Japanese took 1.3401744365692139s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3599934577941895s
Currency | Creation date check for DBpedia in Japanese took 2.6966984272003174s
Currency | Modification date check for DBpedia in Japanese took 2.6665146350860596s
Rep.Conc. | URIs length for DBpedia in Japanese took 110.45160579681396s
Interoperability | New vocabularies check for DBpedia in Japanese took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3315579891204834s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3543272018432617s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.346350908279419s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 2.9233555793762207s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02592301368713379s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.02854776382446289s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4748246669769287s
Consistency | Check Misplaced properties for DBpedia in Japanese took 62.63501977920532s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 1.3172261714935303s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 2.7501490116119385s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03539609909057617s
Security | Sign check for DBpedia in Japanese took 1.3141391277313232s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 20.539083003997803s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.4888591766357422s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 2.1457672119140625e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-ja took 845.1930949687958s
Availability | SPARQL endpoint availability check for dbpedia lite took 9.107589721679688e-05s
Availability | VoID file availability check for dbpedia lite took 0.0007722377777099609s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.3394596576690674s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.822845458984375e-05s
Believability | Calculation of trust value for dbpedia lite took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-lite took 6.805526256561279s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.24939870834350586s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.38507556915283203s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02278423309326172s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00015997886657714844s
Believability | Calculation of trust value for DBpedia in Dutch took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-nl took 3.9676873683929443s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 22.00706195831299s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.3859243392944336s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 7.939338684082031e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-pt took 40.00037217140198s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 8.0108642578125e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.3620645999908447s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.0214688777923584s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.651878356933594e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.1205673217773438e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.807152032852173s
Availability | SPARQL endpoint availability check for DBTropes took 0.00013113021850585938s
Availability | VoID file availability check for DBTropes took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for DBTropes took 0.35048747062683105s
Reputation | Calculation of the PageRank for DBTropes took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.059906005859375e-05s
Believability | Calculation of trust value for DBTropes took 1.2159347534179688e-05s
INFO | --- Analysis for dbtropes took 3.723923444747925s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 9.322166442871094e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.3523740768432617s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020858049392700195s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.3882598876953125e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.1444091796875e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 3.403721570968628s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 9.202957153320312e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.35388875007629395s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.021350860595703125s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.337860107421875e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 3.3756630420684814s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.563133478164673s
Availability | VoID file availability check for DBTune.org/classical took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.3498365879058838s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.390975952148438e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.0251998901367188e-05s
INFO | --- Analysis for dbtune-classical took 9.47247838973999s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.554243564605713s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.35811781883239746s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.771087646484375e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.2874603271484375e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 11.464300394058228s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.553075790405273s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.34240102767944336s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.842613220214844e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.1205673217773438e-05s
INFO | --- Analysis for dbtune-magnatune took 10.317148208618164s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 0.12403702735900879s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005469322204589844s
Extra | Recovery of all triples for DBTune.org Musicbrainz D2R Server took 21.150083780288696s
Performance | Total latancy measurement for DBTune.org Musicbrainz D2R Server took 0.5581333637237549s
Amount of data | Number of triples check for DBTune.org Musicbrainz D2R Server took 0.41977906227111816s
Versatility | Languages check for DBTune.org Musicbrainz D2R Server took 0.17813730239868164s
Interpretability | Number of blank nodes check for DBTune.org Musicbrainz D2R Server took 0.35817456245422363s
Interpretability | RDF structures check for DBTune.org Musicbrainz D2R Server took 0.12105178833007812s
Versatility | Serialization formats check for DBTune.org Musicbrainz D2R Server took 0.11259341239929199s
Availability | RDF dump link check for DBTune.org Musicbrainz D2R Server took 0.09385108947753906s
License | MR license check for DBTune.org Musicbrainz D2R Server took 0.09984207153320312s
License | HR license check for DBTune.org Musicbrainz D2R Server took 0.1474609375s
Amount of data | Number of property check for DBTune.org Musicbrainz D2R Server took 0.11214637756347656s
Understandability | Number of label check for DBTune.org Musicbrainz D2R Server took 0.16067123413085938s
Understandability | URI regex check for DBTune.org Musicbrainz D2R Server took 0.1743307113647461s
Understandability | Vocabs check for DBTune.org Musicbrainz D2R Server took 0.09153461456298828s
Verifiability | Authors check for DBTune.org Musicbrainz D2R Server took 0.08471512794494629s
Verifiability | Publishers check for DBTune.org Musicbrainz D2R Server took 0.0991661548614502s
Amount of data | Check the number of entities for DBTune.org Musicbrainz D2R Server took 3.24249267578125e-05s
Verifiability | Contribs. check for DBTune.org Musicbrainz D2R Server took 0.09149670600891113s
Interlinking | sameAs chians check for DBTune.org Musicbrainz D2R Server took 0.10118794441223145s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.11949539184570312s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.08513951301574707s
Timeliness | dataset update frequency check for DBTune.org Musicbrainz D2R Server took 0.09253311157226562s
Currency | Creation date check for DBTune.org Musicbrainz D2R Server took 0.2271130084991455s
Currency | Modification date check for DBTune.org Musicbrainz D2R Server took 0.21918416023254395s
Rep.Conc. | URIs length for DBTune.org Musicbrainz D2R Server took 1.949728012084961s
Interoperability | New vocabularies check for DBTune.org Musicbrainz D2R Server took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for DBTune.org Musicbrainz D2R Server took 0.11172842979431152s
Consistency | Disjoint class check for DBTune.org Musicbrainz D2R Server took 0.09189271926879883s
Consistency | Check Misplaced properties for DBTune.org Musicbrainz D2R Server took 0.47460246086120605s
Consistency | Check Ontology hijacking for DBTune.org Musicbrainz D2R Server took 4.220220327377319s
Consistency | Check Invalid usage of undefined properties for DBTune.org Musicbrainz D2R Server took 1.485337734222412s
Conciseness | Check Extensional conciseness for DBTune.org Musicbrainz D2R Server took 0.0001342296600341797s
Security | Sign check for DBTune.org Musicbrainz D2R Server took 0.08474850654602051s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.3848836421966553s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for DBTune.org Musicbrainz D2R Server took 9.5367431640625e-07s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.049041748046875e-05s
INFO | --- Analysis for dbtune-musicbrainz took 45.47712588310242s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.45481014251708984s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.3798182010650635s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 4.935264587402344e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.1205673217773438e-05s
INFO | --- Analysis for dbtune-myspace took 3.8574681282043457s
Availability | SPARQL endpoint availability check for data.dcs took 9.179115295410156e-05s
Availability | VoID file availability check for data.dcs took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for data.dcs took 0.33655858039855957s
Reputation | Calculation of the PageRank for data.dcs took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for data.dcs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data.dcs took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.198883056640625e-05s
Believability | Calculation of trust value for data.dcs took 9.298324584960938e-06s
INFO | --- Analysis for dcs-sheffield took 3.3271331787109375s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.601478576660156e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.3702082633972168s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.001018524169921875s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.9591064453125e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.3113021850585938e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 5.185212850570679s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 9.5367431640625e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.364910364151001s
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 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.291534423828125e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.239776611328125e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.39432168006897s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 5.7220458984375e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.326308012008667s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.24249267578125e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.2874603271484375e-05s
INFO | --- Analysis for desaparecidos took 3.6510536670684814s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 9.083747863769531e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.34030914306640625s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.608268737792969e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.1205673217773438e-05s
INFO | --- Analysis for deustoentrepreneurship took 4.724033832550049s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 0.00012636184692382812s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.36965298652648926s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010347366333007812s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.2874603271484375e-05s
INFO | --- Analysis for deustotech took 5.38485312461853s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.5088858604431152s
Availability | VoID file availability check for Deutsche Biographie took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.3664727210998535s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.100799560546875e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.2874603271484375e-05s
INFO | --- Analysis for deutsche-biographie took 5.184610366821289s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 0.0001342296600341797s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.3417022228240967s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020380735397338867s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.221366882324219e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.2159347534179688e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 13.950692892074585s
Availability | SPARQL endpoint availability check for dev8d took 0.000118255615234375s
Availability | VoID file availability check for dev8d took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for dev8d took 0.3330729007720947s
Reputation | Calculation of the PageRank for dev8d took 0.021134138107299805s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.747245788574219e-05s
Believability | Calculation of trust value for dev8d took 1.5497207641601562e-05s
INFO | --- Analysis for dev8d took 4.253735780715942s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.223926782608032s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.3676753044128418s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 4.982948303222656e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.0013580322265625e-05s
INFO | --- Analysis for dewey_decimal_classification took 93.59778213500977s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 9.036064147949219e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.3565254211425781s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.361701965332031e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.1205673217773438e-05s
INFO | --- Analysis for DHSVM took 26.8915057182312s
Availability | SPARQL endpoint availability check for Diavgeia took 9.870529174804688e-05s
Availability | VoID file availability check for Diavgeia took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.32565736770629883s
Reputation | Calculation of the PageRank for Diavgeia took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.20159912109375e-05s
Believability | Calculation of trust value for Diavgeia took 7.62939453125e-06s
INFO | --- Analysis for diavgeia took 6.117492198944092s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.3490009307861328s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.021241426467895508s
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.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011706352233886719s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for didactalia took 7.157512187957764s
Availability | SPARQL endpoint availability check for DisGeNET took 2.4541513919830322s
Availability | VoID file availability check for DisGeNET took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.36142754554748535s
Reputation | Calculation of the PageRank for DisGeNET took 0.0208587646484375s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.000148773193359375s
Believability | Calculation of trust value for DisGeNET took 1.0728836059570312e-05s
INFO | --- Analysis for disgenet took 10.78760838508606s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 8.988380432128906e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.35689711570739746s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02161383628845215s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 2.8848648071289062e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.1444091796875e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 10.222663640975952s
Availability | SPARQL endpoint availability check for DM2E took 9.322166442871094e-05s
Availability | VoID file availability check for DM2E took 0.0007355213165283203s
Completeness | Calculation of interlinking completeness for DM2E took 0.3307523727416992s
Reputation | Calculation of the PageRank for DM2E took 0.021001100540161133s
Interlinking | Calculation of Degree of Connection for DM2E took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011301040649414062s
Believability | Calculation of trust value for DM2E took 1.1444091796875e-05s
INFO | --- Analysis for dm2e took 3.849555492401123s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 9.417533874511719e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.39394354820251465s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015234947204589844s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 8.58306884765625e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 8.332755088806152s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.506111145019531e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.3294811248779297s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.022034168243408203s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.389617919921875e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 4.0531158447265625e-06s
INFO | --- Analysis for doi took 8.65619969367981s
Availability | SPARQL endpoint availability check for Driggu Florentino took 9.1552734375e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.3893105983734131s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.022139549255371094s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.123283386230469e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.239776611328125e-05s
INFO | --- Analysis for Driggu took 4.223912477493286s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 1.169004201889038s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.37973713874816895s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.218650817871094e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.2874603271484375e-05s
INFO | --- Analysis for drug-data-hifm took 17.729130029678345s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.2683575153351s
Availability | VoID file availability check for MetaLex Document Server took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.34328603744506836s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02250361442565918s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.147125244140625e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.2874603271484375e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 554.8555920124054s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.1268982887268066s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.3774740695953369s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.022235870361328125s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.315376281738281e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.3828277587890625e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 15.726420640945435s
Availability | SPARQL endpoint availability check for DWS-Group took 9.179115295410156e-05s
Availability | VoID file availability check for DWS-Group took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.3515665531158447s
Reputation | Calculation of the PageRank for DWS-Group took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010204315185546875s
Believability | Calculation of trust value for DWS-Group took 1.2874603271484375e-05s
INFO | --- Analysis for dws-group took 3.3441944122314453s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 9.1552734375e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.33836960792541504s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.9325485229492188e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.2874603271484375e-05s
INFO | --- Analysis for E1 took 4.753778457641602s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.049828529357910156s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.3392627239227295s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02274942398071289s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011205673217773438s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-alaska took 3.293576717376709s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.06240653991699219s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.3657817840576172s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.2928924560546875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-cau took 3.3960587978363037s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.04086709022521973s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.36414098739624023s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.389617919921875e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 3.2377521991729736s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.07821297645568848s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.3430202007293701s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.022092103958129883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0009350776672363281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 0.00012993812561035156s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-cdrewu took 3.3396170139312744s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.04529380798339844s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.3691859245300293s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.021013975143432617s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001316070556640625s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-dartmouth took 3.2261855602264404s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04781055450439453s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.32503390312194824s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.021468162536621094s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 9.775161743164062e-06s
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.059906005859375e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-famu took 3.2836925983428955s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04882168769836426s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.33939504623413086s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012421607971191406s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-harvard took 3.311913251876831s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.04319286346435547s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.3288888931274414s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020406007766723633s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012540817260742188s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-hawaii took 3.2609052658081055s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.0415804386138916s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.3487675189971924s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0008094310760498047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.103515625e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-howard took 3.17382550239563s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.04815983772277832s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.46257758140563965s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020917654037475586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.532669067382812e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 3.399125099182129s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04332995414733887s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.36474084854125977s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011587142944335938s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-jsu took 3.2615928649902344s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.039159297943115234s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.3371753692626953s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.0208892822265625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.933906555175781e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-meharry took 3.1744983196258545s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.045436859130859375s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.34256434440612793s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02218914031982422s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010180473327636719s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-montana took 3.205188751220703s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.052059173583984375s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.36629343032836914s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.02131509780883789s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.703636169433594e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.8835067749023438e-05s
INFO | --- Analysis for eagle-i-msm took 3.2255899906158447s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.06630158424377441s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.38797736167907715s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.022574186325073242s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00013399124145507812s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-ohsu took 3.324965238571167s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.04196333885192871s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.36922621726989746s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 7.653236389160156e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-psm took 3.2935779094696045s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.05266976356506348s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.34963512420654297s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 7.104873657226562e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-tsu took 3.2067196369171143s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.042199134826660156s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.3585166931152344s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.914138793945312e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-tuskegee took 3.3095321655273438s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.050585031509399414s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.3368501663208008s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.021552085876464844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.34600830078125e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-uccaribe took 3.2763309478759766s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.035527706146240234s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.35955142974853516s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02122330665588379s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012135505676269531s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-upr took 3.1608376502990723s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.050267934799194336s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.3397023677825928s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020925045013427734s
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.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-utep took 3.2761149406433105s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.04281282424926758s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.3494741916656494s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.699562072753906e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-utsa took 3.252408742904663s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.15517187118530273s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.3178844451904297s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02056407928466797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 0.00011754035949707031s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 3.5222816467285156s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.04629826545715332s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.34092044830322266s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.319450378417969e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-xula took 3.3543732166290283s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6175327301025391s
Availability | VoID file availability check for Emergency situation took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.36533355712890625s
Reputation | Calculation of the PageRank for Emergency situation took 0.020496845245361328s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.7206878662109375e-05s
Believability | Calculation of trust value for Emergency situation took 1.2874603271484375e-05s
INFO | --- Analysis for Earthquake took 4.5044848918914795s
Availability | SPARQL endpoint availability check for ESO took 0.45581769943237305s
Availability | VoID file availability check for ESO took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for ESO took 0.324617862701416s
Reputation | Calculation of the PageRank for ESO took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for ESO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for ESO took 8.249282836914062e-05s
Believability | Calculation of trust value for ESO took 4.5299530029296875e-06s
INFO | --- Analysis for Earthquake_case took 4.432195425033569s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.12006449699401855s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.3419504165649414s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010204315185546875s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for ecb-linked-data took 3.348567485809326s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 7.918190956115723s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.3694121837615967s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.4809112548828125e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 9.5367431640625e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 18.58014464378357s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.8173117637634277s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.3577876091003418s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.508827209472656e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 20.36245369911194s
Availability | SPARQL endpoint availability check for ECLAP took 20.565412521362305s
Availability | VoID file availability check for ECLAP took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for ECLAP took 0.34832096099853516s
Reputation | Calculation of the PageRank for ECLAP took 0.02115011215209961s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.814697265625e-05s
Believability | Calculation of trust value for ECLAP took 1.2159347534179688e-05s
INFO | --- Analysis for eclap took 53.863213539123535s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.553794860839844e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.361344575881958s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.021567821502685547s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.000972747802734375s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.2874603271484375e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.2636184692382812e-05s
INFO | --- Analysis for ECNU-GISer took 5.024170637130737s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 5.698204040527344e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.3366520404815674s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02125096321105957s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0010406970977783203s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 6.461143493652344e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.1682510375976562e-05s
INFO | --- Analysis for ecs took 3.170161724090576s
Availability | SPARQL endpoint availability check for Edublogs took 9.107589721679688e-05s
Availability | VoID file availability check for Edublogs took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Edublogs took 0.32540106773376465s
Reputation | Calculation of the PageRank for Edublogs took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010228157043457031s
Believability | Calculation of trust value for Edublogs took 1.0967254638671875e-05s
INFO | --- Analysis for edublogs took 4.20415735244751s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5345754623413086s
Availability | VoID file availability check for education.data.gov.uk took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.3429534435272217s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 0.00012350082397460938s
Believability | Calculation of trust value for education.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for education-data-gov-uk took 6.328810453414917s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.2682580947876s
Availability | VoID file availability check for Educational programs - SISVU took 0.0007543563842773438s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.698868989944458s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.316734313964844e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.2159347534179688e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1322.7871239185333s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 5.344075918197632s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.3806290626525879s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.38690185546875e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 8.821487426757812e-06s
INFO | --- Analysis for eea took 19.250844955444336s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5275545120239258s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.3642153739929199s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020973920822143555s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.507469177246094e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 9.059906005859375e-06s
INFO | --- Analysis for eea-rod took 5.988080739974976s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.1736609935760498s
Availability | VoID file availability check for EEA Vocabularies took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.32534217834472656s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.022150278091430664s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.273124694824219e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.0251998901367188e-05s
INFO | --- Analysis for eea-vocabularies took 5.903579473495483s
Availability | SPARQL endpoint availability check for E-Government Ontology took 20.48236918449402s
Availability | VoID file availability check for E-Government Ontology took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.35591769218444824s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for EGovOntology took 34.30630612373352s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5396678447723389s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005826950073242188s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.0158023834228516s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3155338764190674s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6306447982788086s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9682633876800537s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.37986731529236s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.738666296005249s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5798521041870117s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8653349876403809s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24020838737487793s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4886958599090576s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 5.902547121047974s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2873523235321045s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40941500663757324s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6062207221984863s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3134419918060303s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3200232982635498s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2526247501373291s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.74197769165039s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 8.130073547363281e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.35367822647094727s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2799105644226074s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.41200685501098633s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24504971504211426s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2940714359283447s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.938833475112915s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24948382377624512s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 6.056718111038208s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2757885456085205s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.34734487533569336s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3431735038757324s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3518972396850586s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030704498291015625s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.028207778930664062s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26377272605895996s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.3676958084106445s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5105242729187012s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.3446953296661377s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2728359699249268s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.153392553329468s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03402256965637207s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.45662522315979004s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5376770496368408s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3236.5361297130585s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7975835800170898s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.025553226470947266s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9073486328125e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3113021850585938e-05s
INFO | --- Analysis for ei2a took 3479.202274799347s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 9.34600830078125e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.3410060405731201s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010943412780761719s
Believability | Calculation of trust value for EIONET RDF Data took 9.5367431640625e-06s
INFO | --- Analysis for eionet-rdf took 3.756012439727783s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.649162292480469e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.3399467468261719s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.021982431411743164s
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.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.0040740966796875e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.049041748046875e-05s
INFO | --- Analysis for ElgooG_ took 3.252718687057495s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.16958999633789s
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.3429141044616699s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.939338684082031e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.0728836059570312e-05s
INFO | --- Analysis for elviajero took 22.729806184768677s
Availability | SPARQL endpoint availability check for EMN took 8.845329284667969e-05s
Availability | VoID file availability check for EMN took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for EMN took 0.3156435489654541s
Reputation | Calculation of the PageRank for EMN took 0.022655963897705078s
Interlinking | Calculation of Degree of Connection for EMN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for EMN took 4.029273986816406e-05s
Believability | Calculation of trust value for EMN took 5.4836273193359375e-06s
INFO | --- Analysis for emn took 3.3300342559814453s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 8.797645568847656e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.3916022777557373s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02082347869873047s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.1021575927734375e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 8.106231689453125e-06s
INFO | --- Analysis for enakting-co2emission took 3.3771774768829346s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.00048828125s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.34767603874206543s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.9577484130859375e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-crime took 3.248236656188965s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 9.059906005859375e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.36370849609375s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.0204925537109375s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.8623809814453125e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 8.106231689453125e-06s
INFO | --- Analysis for enakting-energy took 3.4438209533691406s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.982948303222656e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.3289668560028076s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.022362947463989258s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 8.96453857421875e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-mortality took 3.159655809402466s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 9.298324584960938e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.3657853603363037s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.021783113479614258s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.8623809814453125e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-nhs took 3.220332384109497s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 9.131431579589844e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.3340773582458496s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.435943603515625e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-population took 3.21683406829834s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.7450151443481445s
Availability | VoID file availability check for English Heritage Periods List took 0.0007381439208984375s
Extra | Recovery of all triples for English Heritage Periods List took 0.3320920467376709s
Performance | Total latancy measurement for English Heritage Periods List took 1.5204713344573975s
Amount of data | Number of triples check for English Heritage Periods List took 0.48952174186706543s
Versatility | Languages check for English Heritage Periods List took 0.27315807342529297s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5389869213104248s
Security | Check HTTPS for English Heritage Periods List took 0.22029685974121094s
Interpretability | RDF structures check for English Heritage Periods List took 0.2682826519012451s
Versatility | Serialization formats check for English Heritage Periods List took 0.4871490001678467s
Availability | RDF dump link check for English Heritage Periods List took 0.28166866302490234s
License | MR license check for English Heritage Periods List took 0.5092473030090332s
License | HR license check for English Heritage Periods List took 0.32553839683532715s
Amount of data | Number of property check for English Heritage Periods List took 0.3301873207092285s
Understandability | Number of label check for English Heritage Periods List took 0.5008516311645508s
Understandability | URI regex check for English Heritage Periods List took 0.6357603073120117s
Understandability | Vocabs check for English Heritage Periods List took 0.33402037620544434s
Verifiability | Authors check for English Heritage Periods List took 0.3510477542877197s
Verifiability | Publishers check for English Heritage Periods List took 0.32577013969421387s
Performance | Throughput check for English Heritage Periods List took 12.708309412002563s
Amount of data | Check the number of entities for English Heritage Periods List took 8.916854858398438e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.302778959274292s
Interlinking | sameAs chians check for English Heritage Periods List took 0.32778048515319824s
Interlinking | skos check for English Heritage Periods List took 0.32432126998901367s
Interlinking | skos check for English Heritage Periods List took 0.349790096282959s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.3981339931488037s
Currency | Creation date check for English Heritage Periods List took 0.6483945846557617s
Currency | Modification date check for English Heritage Periods List took 0.7339162826538086s
Rep.Conc. | URIs length for English Heritage Periods List took 0.612598180770874s
Interoperability | New vocabularies check for English Heritage Periods List took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.30661463737487793s
Accuracy | Check Functional Property for English Heritage Periods List took 0.2974402904510498s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3035123348236084s
Consistency | Disjoint class check for English Heritage Periods List took 0.31874990463256836s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.31008243560791016s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.5856804847717285s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00014162063598632812s
Security | Sign check for English Heritage Periods List took 0.31006598472595215s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.3570113182067871s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.3855438232421875e-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 1.2874603271484375e-05s
INFO | --- Analysis for english-heritage-periods-list took 55.63839650154114s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.44199109077453613s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0006420612335205078s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 5.965206146240234s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.306455135345459s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.400909423828125s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.6682701110839844s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.636422872543335s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.172091484069824s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.16095948219299316s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.3367500305175781s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.22246718406677246s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 51.42995500564575s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.8431999683380127s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.225454807281494s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.1590256690979004s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.32158684730529785s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.4187629222869873s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.2135629653930664s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.21443867683410645s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.2304534912109375s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.511213779449463s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 3.2901763916015625e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.15551161766052246s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.3048083782196045s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.6267242431640625s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.19333124160766602s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.15365004539489746s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.5354597568511963s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.29868483543395996s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.4668772220611572s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.16585135459899902s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.16098356246948242s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.20170116424560547s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.3360297679901123s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.7146434783935547s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 0.9698381423950195s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.6030960083007812s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0001614093780517578s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.36997342109680176s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.21904587745666504s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.4624183177947998s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 8.58306884765625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 281.93499970436096s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.16074538230895996s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0006372928619384766s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.152433156967163s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.943934440612793s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.7031126022338867s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.5368320941925049s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.4401884078979492s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.25359058380127s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.18752050399780273s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.13618254661560059s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.21277475357055664s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 46.96028232574463s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.5182154178619385s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.17086124420166s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.14805364608764648s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.15148210525512695s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.3361539840698242s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.2070913314819336s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.19997143745422363s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.15290498733520508s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 10.821531057357788s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 4.220008850097656e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.14885950088500977s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.375946044921875s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.20008134841918945s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.21498847007751465s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.20888018608093262s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.42787742614746094s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.2028653621673584s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.5262045860290527s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.19624996185302734s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.15463733673095703s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.16193199157714844s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.13976550102233887s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.39173078536987305s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 2.6612112522125244s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.5249264240264893s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00016045570373535156s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.2325732707977295s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.6805243492126465s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.3594076633453369s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.021350383758544922s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 4.291534423828125e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 8.344650268554688e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 265.5443592071533s
Availability | SPARQL endpoint availability check for English WordNet took 8.940696716308594e-05s
Availability | VoID file availability check for English WordNet took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for English WordNet took 0.36664605140686035s
Reputation | Calculation of the PageRank for English WordNet took 0.021212339401245117s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.600120544433594e-05s
Believability | Calculation of trust value for English WordNet took 1.2874603271484375e-05s
INFO | --- Analysis for english-wordnet took 4.001735210418701s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.1091153621673584s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.3654005527496338s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.021703243255615234s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 0.00011181831359863281s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.430511474609375e-05s
INFO | --- Analysis for enipedia took 3.288926362991333s
Availability | SPARQL endpoint availability check for Enslaved.org took 8.749961853027344e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.32860398292541504s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.075599670410156e-05s
Believability | Calculation of trust value for Enslaved.org took 1.0013580322265625e-05s
INFO | --- Analysis for enslaved.org took 5.6971728801727295s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 5.350652694702148s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.3258845806121826s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.021776199340820312s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.6743621826171875e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.3828277587890625e-05s
INFO | --- Analysis for entice-graph took 8.731867790222168s
Availability | SPARQL endpoint availability check for Entrez Gene took 8.988380432128906e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008518695831298828s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.3507959842681885s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.361701965332031e-05s
Believability | Calculation of trust value for Entrez Gene took 1.33514404296875e-05s
INFO | --- Analysis for entrez_gene took 30.302117586135864s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.017000436782837s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.3414123058319092s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.021396160125732422s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.9114227294921875e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 8.344650268554688e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.424968004226685s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.314359188079834s
Availability | VoID file availability check for environment.data.gov.uk took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.31665945053100586s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.696846008300781e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 8.821487426757812e-06s
INFO | --- Analysis for environment-data-gov-uk took 10.402473449707031s
Availability | SPARQL endpoint availability check for EARTh took 270.3861906528473s
Availability | VoID file availability check for EARTh took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for EARTh took 0.36583709716796875s
Reputation | Calculation of the PageRank for EARTh took 0.021174192428588867s
Interlinking | Calculation of Degree of Connection for EARTh took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010514259338378906s
Believability | Calculation of trust value for EARTh took 1.3589859008789062e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 564.0977590084076s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.6157879829406738s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0005159378051757812s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 123.70216012001038s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 1.0210850238800049s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.436218023300171s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.094984769821167s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.1939899921417s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.0611984729766846s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.334075927734375s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 8.63734745979309s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.35979437828063965s
License | MR license check for Micka (EO metadata) @PSNC took 0.6832785606384277s
License | HR license check for Micka (EO metadata) @PSNC took 300.22642278671265s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.2267448902130127s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 3.214815139770508s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 1.2466306686401367s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.6796128749847412s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.2033233642578125s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.24919867515563965s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.407611608505249s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 7.62939453125e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.19166040420532227s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.19378662109375s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.5019521713256836s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4000668525695801s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 6.078749418258667s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.503373384475708s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.2691323757171631s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 153.20454478263855s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.216627836227417s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.5006661415100098s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.42554712295532227s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 34.814860343933105s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.665977954864502s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.5993361473083496s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.1993694305419922s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 87.19514679908752s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.13955807685852s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 35.53711819648743s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.3305184841156006s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 88.12056517601013s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.7869439125061035s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5737755298614502s
Security | Sign check for Micka (EO metadata) @PSNC took 1.9829697608947754s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 9.411054372787476s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.609757661819458s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021337509155273438s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for EO_metadata took 2279.5604939460754s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.458427429199219e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.33507299423217773s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.4809112548828125e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 8.821487426757812e-06s
INFO | --- Analysis for EOKP-Datasets took 3.878253698348999s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.482269287109375e-05s
Availability | VoID file availability check for EPA-CDR took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.33301401138305664s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.647804260253906e-05s
Believability | Calculation of trust value for EPA-CDR took 5.0067901611328125e-06s
INFO | --- Analysis for epa-cdr took 7.584096431732178s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.506111145019531e-05s
Availability | VoID file availability check for EPA-FRS took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.32716941833496094s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.486343383789062e-05s
Believability | Calculation of trust value for EPA-FRS took 5.245208740234375e-06s
INFO | --- Analysis for epa-frs took 7.3906121253967285s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.792213439941406e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.3150515556335449s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.314018249511719e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.245208740234375e-06s
INFO | --- Analysis for epa-rcra took 6.502501010894775s
Availability | SPARQL endpoint availability check for EPA-SRS took 9.608268737792969e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.35218071937561035s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 8.082389831542969e-05s
Believability | Calculation of trust value for EPA-SRS took 9.059906005859375e-06s
INFO | --- Analysis for epa-srs took 6.816386699676514s
Availability | SPARQL endpoint availability check for EPA-TRI took 9.059906005859375e-05s
Availability | VoID file availability check for EPA-TRI took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.3441035747528076s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020679950714111328s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.528594970703125e-05s
Believability | Calculation of trust value for EPA-TRI took 9.059906005859375e-06s
INFO | --- Analysis for epa-tri took 6.958839416503906s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.027296066284179688s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.33013105392456055s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013017654418945312s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 3.195415735244751s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.4557983875274658s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.348846435546875s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.273124694824219e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 8.58306884765625e-06s
INFO | --- Analysis for eprtr took 4.416256666183472s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.5418202877044678s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0006747245788574219s
Extra | Recovery of all triples for Railway Infrastructure KG took 59.75572180747986s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.1279244422912598s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.27092981338500977s
Interoperability | New terms check for Railway Infrastructure KG took 1.685610055923462s
Versatility | Languages check for Railway Infrastructure KG took 92.42005443572998s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.26659274101257324s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.7004077434539795s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.25046706199645996s
Availability | RDF dump link check for Railway Infrastructure KG took 0.23734498023986816s
License | MR license check for Railway Infrastructure KG took 0.2960183620452881s
License | HR license check for Railway Infrastructure KG took 106.28185820579529s
Amount of data | Number of property check for Railway Infrastructure KG took 0.23871755599975586s
Understandability | Number of label check for Railway Infrastructure KG took 0.8075573444366455s
Understandability | URI regex check for Railway Infrastructure KG took 0.5078606605529785s
Understandability | Vocabs check for Railway Infrastructure KG took 0.281754732131958s
Verifiability | Authors check for Railway Infrastructure KG took 0.35805654525756836s
Verifiability | Publishers check for Railway Infrastructure KG took 0.2892000675201416s
Performance | Throughput check for Railway Infrastructure KG took 11.416690826416016s
Amount of data | Check the number of entities for Railway Infrastructure KG took 1.0841619968414307s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.2897932529449463s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.2696232795715332s
Interlinking | skos check for Railway Infrastructure KG took 0.27208971977233887s
Interlinking | skos check for Railway Infrastructure KG took 0.22829365730285645s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.27198147773742676s
Currency | Creation date check for Railway Infrastructure KG took 0.48317432403564453s
Currency | Modification date check for Railway Infrastructure KG took 0.249650239944458s
Rep.Conc. | URIs length for Railway Infrastructure KG took 28.68298888206482s
Interoperability | New vocabularies check for Railway Infrastructure KG took 116.47166085243225s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.30637407302856445s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.23949003219604492s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.27138328552246094s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 15.412140130996704s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.5994937419891357s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.6104557514190674s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.24863505363464355s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 2.3323700428009033s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.375535249710083s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 19.323501586914062s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.490403413772583s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 3.106780529022217s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.9369094371795654s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.41281580924987793s
Security | Sign check for Railway Infrastructure KG took 0.8631646633148193s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2772.1515424251556s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.6724646091461182s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.024153470993041992s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 6.628036499023438e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 139.7091839313507s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.3589859008789062e-05s
INFO | --- Analysis for ERAKG took 3570.9388241767883s
Availability | SPARQL endpoint availability check for reg took 4.4345855712890625e-05s
Availability | VoID file availability check for reg took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for reg took 0.3620028495788574s
Reputation | Calculation of the PageRank for reg took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for reg took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for reg took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for reg took 1.1682510375976562e-05s
Believability | Calculation of trust value for reg took 1.3589859008789062e-05s
INFO | --- Analysis for erg took 3.3785245418548584s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.31046319007873535s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.36469006538391113s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020873546600341797s
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.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.2901763916015625e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 8.344650268554688e-06s
INFO | --- Analysis for es-msssi-drug-prices took 4.037297248840332s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 8.869171142578125e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.3621654510498047s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02089715003967285s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 0.00010323524475097656s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 9.059906005859375e-06s
INFO | --- Analysis for esd-standards took 5.436236143112183s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 0.00010561943054199219s
Availability | VoID file availability check for ESD-Toolkit took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.42180538177490234s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.021584749221801758s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 8.249282836914062e-05s
Believability | Calculation of trust value for ESD-Toolkit took 8.821487426757812e-06s
INFO | --- Analysis for esd-toolkit took 4.713181734085083s
Availability | SPARQL endpoint availability check for Dataset Esis took 9.465217590332031e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.389312744140625s
Reputation | Calculation of the PageRank for Dataset Esis took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 2.86102294921875e-05s
Believability | Calculation of trust value for Dataset Esis took 1.3589859008789062e-05s
INFO | --- Analysis for esislearning took 3.9179136753082275s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 0.0002999305725097656s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.36005282402038574s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 2.956390380859375e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.0013580322265625e-05s
INFO | --- Analysis for ESV took 4.688250303268433s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.9265270233154297s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0012316703796386719s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.39130306243896484s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 5.571290493011475s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 7.848515510559082s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.41192173957824707s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.271766662597656e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.3828277587890625e-05s
INFO | --- Analysis for eu-agencies-bodies took 23.19934844970703s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.893013000488281e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.38866543769836426s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.462501525878906e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 8.344650268554688e-06s
INFO | --- Analysis for eu-institutions took 10.445780515670776s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.3578267097473145s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.39336585998535156s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02157449722290039s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 4.601478576660156e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 9.298324584960938e-06s
INFO | --- Analysis for eu-parliament-media took 11.294253587722778s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.5936660766601562s
Availability | VoID file availability check for EU Who Is Who took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.3630259037017822s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020735502243041992s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.314018249511719e-05s
Believability | Calculation of trust value for EU Who Is Who took 9.5367431640625e-06s
INFO | --- Analysis for eu-who-is-who took 17.271191120147705s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.6512467861175537s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.39192914962768555s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.02054429054260254s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.9577484130859375e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for eumida-linked-data took 13.990366458892822s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.4115276336669922s
Availability | VoID file availability check for European Nature Information System took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.3642871379852295s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010943412780761719s
Believability | Calculation of trust value for European Nature Information System took 1.3589859008789062e-05s
INFO | --- Analysis for eunis took 5.36069917678833s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 8.49375033378601s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.38966941833496094s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.05718994140625e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for eur-lex-rdf took 22.1989905834198s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.2735559940338135s
Availability | VoID file availability check for Standard Eurobarometer took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.36417722702026367s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.1961669921875e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 9.059906005859375e-06s
INFO | --- Analysis for eurobarometer-standard took 13.419377088546753s
Availability | SPARQL endpoint availability check for European Election Results took 1.4923317432403564s
Availability | VoID file availability check for European Election Results took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for European Election Results took 0.3935575485229492s
Reputation | Calculation of the PageRank for European Election Results took 0.02296733856201172s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.4809112548828125e-05s
Believability | Calculation of trust value for European Election Results took 9.5367431640625e-06s
INFO | --- Analysis for european-election-results took 13.773615598678589s
Availability | SPARQL endpoint availability check for EPO patents took 0.4431791305541992s
Availability | VoID file availability check for EPO patents took 0.0006051063537597656s
Extra | Recovery of all triples for EPO patents took 24.0191068649292s
Performance | Total latancy measurement for EPO patents took 1.1180615425109863s
Amount of data | Number of triples check for EPO patents took 90.18487906455994s
Versatility | Languages check for EPO patents took 100.22136235237122s
Interpretability | Number of blank nodes check for EPO patents took 90.234055519104s
Interpretability | RDF structures check for EPO patents took 0.29830455780029297s
Versatility | Serialization formats check for EPO patents took 0.2971930503845215s
Availability | RDF dump link check for EPO patents took 0.2279515266418457s
License | MR license check for EPO patents took 0.29790449142456055s
License | HR license check for EPO patents took 90.22717595100403s
Amount of data | Number of property check for EPO patents took 0.26674509048461914s
Understandability | Number of label check for EPO patents took 90.19757080078125s
Understandability | URI regex check for EPO patents took 0.5880067348480225s
Understandability | Vocabs check for EPO patents took 0.2780475616455078s
Verifiability | Authors check for EPO patents took 0.25833702087402344s
Verifiability | Publishers check for EPO patents took 0.23304128646850586s
Performance | Throughput check for EPO patents took 11.091084480285645s
Amount of data | Check the number of entities for EPO patents took 7.128715515136719e-05s
Verifiability | Contribs. check for EPO patents took 0.2684924602508545s
Interlinking | sameAs chians check for EPO patents took 0.20662498474121094s
Interlinking | skos check for EPO patents took 0.2189180850982666s
Interlinking | skos check for EPO patents took 0.19128847122192383s
Timeliness | dataset update frequency check for EPO patents took 0.18856549263000488s
Currency | Creation date check for EPO patents took 0.39047861099243164s
Currency | Modification date check for EPO patents took 0.372173547744751s
Rep.Conc. | URIs length for EPO patents took 132.57683086395264s
Interoperability | New vocabularies check for EPO patents took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.23858237266540527s
Accuracy | Check Empty annotation labels for EPO patents took 20.940754890441895s
Accuracy | Check White space in annotation for EPO patents took 2.9749457836151123s
Accuracy | Check Datatype consistency for EPO patents took 4.7634265422821045s
Consistency | Disjoint class check for EPO patents took 0.28182172775268555s
Consistency | Check Misplaced properties for EPO patents took 100.49956750869751s
Consistency | Check Ontology hijacking for EPO patents took 26.971126794815063s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.6208012104034424s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.65986657142639s
Conciseness | Check Extensional conciseness for EPO patents took 2.9394423961639404s
Conciseness | Check Intensional conciseness for EPO patents took 0.38307881355285645s
Security | Sign check for EPO patents took 0.18306612968444824s
Availability | Check URIs Dereferenciability for EPO patents took 2.1101927757263184s
Completeness | Calculation of interlinking completeness for EPO patents took 0.6364650726318359s
Reputation | Calculation of the PageRank for EPO patents took 0.02138233184814453s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for EPO patents took 5.7697296142578125e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.9073486328125e-06s
Believability | Calculation of trust value for EPO patents took 1.4066696166992188e-05s
INFO | --- Analysis for European_Patent_Information took 1198.4254219532013s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 9.274482727050781e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.4159736633300781s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.022450923919677734s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.441375732421875e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.33514404296875e-05s
INFO | --- Analysis for europeana-lod-v1 took 9.290432929992676s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.37775397300720215s
Availability | VoID file availability check for Europeana SPARQL took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.36375975608825684s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.021049022674560547s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.340576171875e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.2874603271484375e-05s
INFO | --- Analysis for europeana-sparql took 6.387329339981079s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.05635380744934082s
Availability | VoID file availability check for EuroSentiment took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.4139668941497803s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02135443687438965s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.790855407714844e-05s
Believability | Calculation of trust value for EuroSentiment took 8.344650268554688e-06s
INFO | --- Analysis for eurosentiment took 4.34326434135437s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 6.198883056640625e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.3902745246887207s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.021735191345214844s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.511543273925781e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 9.775161743164062e-06s
INFO | --- Analysis for eurostat-rdf took 14.330483198165894s
Availability | SPARQL endpoint availability check for EuroVoc took 0.214735746383667s
Availability | VoID file availability check for EuroVoc took 0.0007946491241455078s
Extra | Recovery of all triples for EuroVoc took 211.8488461971283s
Performance | Total latancy measurement for EuroVoc took 0.6262004375457764s
Amount of data | Number of triples check for EuroVoc took 55.69670009613037s
Interoperability | New terms check for EuroVoc took 58.515735387802124s
Versatility | Languages check for EuroVoc took 300.09802508354187s
Interpretability | Number of blank nodes check for EuroVoc took 15.917073249816895s
Security | Check HTTPS for EuroVoc took 0.39110755920410156s
Interpretability | RDF structures check for EuroVoc took 0.5148234367370605s
Versatility | Serialization formats check for EuroVoc took 4.884977340698242s
Availability | RDF dump link check for EuroVoc took 0.23201942443847656s
License | MR license check for EuroVoc took 0.6279749870300293s
License | HR license check for EuroVoc took 300.0747582912445s
Amount of data | Number of property check for EuroVoc took 0.429107666015625s
Understandability | Number of label check for EuroVoc took 3.6306865215301514s
Understandability | URI regex check for EuroVoc took 0.47190284729003906s
Understandability | Vocabs check for EuroVoc took 0.15125632286071777s
Verifiability | Authors check for EuroVoc took 0.3215460777282715s
Verifiability | Publishers check for EuroVoc took 0.24462342262268066s
Performance | Throughput check for EuroVoc took 10.54686713218689s
Amount of data | Check the number of entities for EuroVoc took 0.00010895729064941406s
Verifiability | Contribs. check for EuroVoc took 0.12592148780822754s
Interlinking | sameAs chians check for EuroVoc took 8.586169719696045s
Interlinking | skos check for EuroVoc took 0.4190797805786133s
Interlinking | skos check for EuroVoc took 0.3239765167236328s
Timeliness | dataset update frequency check for EuroVoc took 0.4483065605163574s
Currency | Creation date check for EuroVoc took 0.5496177673339844s
Currency | Modification date check for EuroVoc took 0.23800897598266602s
Rep.Conc. | URIs length for EuroVoc took 404.82166171073914s
Interoperability | New vocabularies check for EuroVoc took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.19893264770507812s
Accuracy | Check Functional Property for EuroVoc took 0.20687603950500488s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.2166156768798828s
Accuracy | Check Empty annotation labels for EuroVoc took 37.28613233566284s
Accuracy | Check White space in annotation for EuroVoc took 3.196305274963379s
Accuracy | Check Datatype consistency for EuroVoc took 2.6125898361206055s
Consistency | Disjoint class check for EuroVoc took 0.1777632236480713s
Consistency | Check Misplaced properties for EuroVoc took 300.44769382476807s
Consistency | Misplaced classes for EuroVoc took 8.431142807006836s
Consistency | Check Ontology hijacking for EuroVoc took 35.18900203704834s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.5259499549865723s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.49660658836365s
Conciseness | Check Extensional conciseness for EuroVoc took 3.096205472946167s
Conciseness | Check Intensional conciseness for EuroVoc took 0.449993371963501s
Security | Sign check for EuroVoc took 0.6617424488067627s
Availability | Check URIs Dereferenciability for EuroVoc took 17.346381425857544s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.8823177814483643s
Reputation | Calculation of the PageRank for EuroVoc took 0.021872997283935547s
Interlinking | Calculation of Degree of Connection for EuroVoc took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 8.559226989746094e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.9073486328125e-06s
Believability | Calculation of trust value for EuroVoc took 1.3589859008789062e-05s
INFO | --- Analysis for eurovoc took 15994.617282629013s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 9.369850158691406e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.3918607234954834s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.022166728973388672s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.506111145019531e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 9.298324584960938e-06s
INFO | --- Analysis for euskadi-farmacias took 6.4259350299835205s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.6559922695159912s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.42060041427612305s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.0994415283203125e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.1205673217773438e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 5.1369898319244385s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.6083130836486816s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.3903632164001465s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 6.961822509765625e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.3113021850585938e-05s
INFO | --- Analysis for eutc-productions took 9.427417516708374s
Availability | SPARQL endpoint availability check for EventMedia took 0.4110140800476074s
Availability | VoID file availability check for EventMedia took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for EventMedia took 0.39638376235961914s
Reputation | Calculation of the PageRank for EventMedia took 0.02106928825378418s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010704994201660156s
Believability | Calculation of trust value for EventMedia took 1.2874603271484375e-05s
INFO | --- Analysis for event-media took 25.9247407913208s
Availability | SPARQL endpoint availability check for EventKG took 4.5299530029296875e-05s
Availability | VoID file availability check for EventKG took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for EventKG took 0.39076757431030273s
Reputation | Calculation of the PageRank for EventKG took 0.022036075592041016s
Interlinking | Calculation of Degree of Connection for EventKG took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0012285709381103516s
Interlinking | Calculation of Clustering coefficient for EventKG took 0.00010442733764648438s
Believability | Calculation of trust value for EventKG took 7.867813110351562e-06s
INFO | --- Analysis for eventkg took 5.9391419887542725s
Availability | SPARQL endpoint availability check for Eventseer took 3.293501615524292s
Availability | VoID file availability check for Eventseer took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Eventseer took 0.3965272903442383s
Reputation | Calculation of the PageRank for Eventseer took 0.02279496192932129s
Interlinking | Calculation of Degree of Connection for Eventseer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eventseer took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.601478576660156e-05s
Believability | Calculation of trust value for Eventseer took 8.58306884765625e-06s
INFO | --- Analysis for eventseer took 6.703481912612915s
Availability | SPARQL endpoint availability check for Face Link took 4.553794860839844e-05s
Availability | VoID file availability check for Face Link took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Face Link took 0.3575255870819092s
Reputation | Calculation of the PageRank for Face Link took 0.021173715591430664s
Interlinking | Calculation of Degree of Connection for Face Link took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.5762786865234375e-05s
Believability | Calculation of trust value for Face Link took 1.2874603271484375e-05s
INFO | --- Analysis for Face_Link took 3.3727498054504395s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6709144115447998s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005419254302978516s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 104.13630628585815s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0467910766601562s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.38727855682373s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.221899271011353s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.23704957962036s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.4357337951660156s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.40579819679260254s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.437403917312622s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.29020261764526367s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.7343595027923584s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2646903991699s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.23577284812927246s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.5289225578308105s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.7400586605072021s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21931695938110352s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.23360705375671387s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.26984453201293945s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.461481809616089s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.00010848045349121094s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21884870529174805s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22019100189208984s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.517566442489624s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4292435646057129s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.7672665119171143s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5281972885131836s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.269212007522583s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 150.0426070690155s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.23088335990905762s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.494382381439209s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22717857360839844s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 34.96322226524353s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6729846000671387s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6406095027923584s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21538519859313965s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 85.67942595481873s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.361485004425049s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 34.47084450721741s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3403327465057373s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 87.02706813812256s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.8533198833465576s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5928757190704346s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3042898178100586s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 13.443335056304932s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6437427997589111s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.245208740234375e-06s
INFO | --- Analysis for FADN_(2019) took 2275.551691532135s
Availability | SPARQL endpoint availability check for FAMEData took 9.131431579589844e-05s
Availability | VoID file availability check for FAMEData took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for FAMEData took 0.36000776290893555s
Reputation | Calculation of the PageRank for FAMEData took 0.022556304931640625s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.0040740966796875e-05s
Believability | Calculation of trust value for FAMEData took 1.2159347534179688e-05s
INFO | --- Analysis for famedata took 5.914721488952637s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 9.059906005859375e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.45240187644958496s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020999908447265625s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010991096496582031s
Believability | Calculation of trust value for FAO geopolitical ontology took 5.4836273193359375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 413.05218482017517s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.1289222240447998s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.38466691970825195s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.02028965950012207s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.775161743164062e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for fao-linked-data took 3.5976412296295166s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 5.53131103515625e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.36562347412109375s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.021063804626464844s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.147125244140625e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for FAO_species took 3.383314609527588s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.752886056900024s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.39250636100769043s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.363059997558594e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.2874603271484375e-05s
INFO | --- Analysis for farmbio-chembl took 66.61265182495117s
Availability | SPARQL endpoint availability check for I4.0-Onto took 8.845329284667969e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.3597133159637451s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02239990234375s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.8848648071289062e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.2159347534179688e-05s
INFO | --- Analysis for fatimazahra took 3.275066614151001s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.410743713378906e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.38932299613952637s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.02206730842590332s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.0994415283203125e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.1682510375976562e-05s
INFO | --- Analysis for FHIR_STU3 took 3.8257455825805664s
Availability | SPARQL endpoint availability check for FiESTA took 6.031990051269531e-05s
Availability | VoID file availability check for FiESTA took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for FiESTA took 0.39266467094421387s
Reputation | Calculation of the PageRank for FiESTA took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.5762786865234375e-05s
Believability | Calculation of trust value for FiESTA took 1.3113021850585938e-05s
INFO | --- Analysis for fiesta took 13.638572216033936s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.000110626220703125s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.36104846000671387s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02197885513305664s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.8133392333984375e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.775161743164062e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 3.3706932067871094s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 9.059906005859375e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.3552525043487549s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.771087646484375e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 9.059906005859375e-06s
INFO | --- Analysis for finnish-municipalities took 4.738187551498413s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.21262598037719727s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0004673004150390625s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 111.11000728607178s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 1.059267520904541s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 9.244183778762817s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.273462533950806s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.2552926540375s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.1234469413757324s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.20850086212158203s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 8.062265157699585s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.21753144264221191s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.2695460319519043s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.2390205860138s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.23992681503295898s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 1.258345603942871s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.6724274158477783s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.21685385704040527s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.22960424423217773s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.26682066917419434s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 10.652992963790894s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 3.3855438232421875e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.21663808822631836s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.22249388694763184s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.44493818283081055s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.41969752311706543s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 5.728902339935303s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.5258829593658447s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.27086377143859863s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 147.7248876094818s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.21317744255065918s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.21666359901428223s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.21703314781188965s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 35.63043284416199s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6758463382720947s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.6789982318878174s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.20994806289672852s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 86.60374903678894s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.337011098861694s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 36.13168406486511s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.3941185474395752s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 86.86768984794617s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.8025705814361572s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.6540012359619141s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.2132256031036377s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 13.878474235534668s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.8230183124542236s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.021090984344482422s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2281.865340948105s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.458427429199219e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.3664846420288086s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.022942781448364258s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.296966552734375e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.2159347534179688e-05s
INFO | --- Analysis for fishes-of-texas took 5.263900518417358s
Availability | SPARQL endpoint availability check for flickr? wrappr took 8.940696716308594e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.3875870704650879s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.393692016601562e-05s
Believability | Calculation of trust value for flickr? wrappr took 9.775161743164062e-06s
INFO | --- Analysis for flickr-wrappr took 4.390387535095215s
Availability | SPARQL endpoint availability check for Future land use simulation model took 9.202957153320312e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.3606102466583252s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 2.86102294921875e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.3113021850585938e-05s
INFO | --- Analysis for FLUS took 10.068431615829468s
Availability | SPARQL endpoint availability check for Flybase took 1.4051015377044678s
Availability | VoID file availability check for Flybase took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Flybase took 0.38785862922668457s
Reputation | Calculation of the PageRank for Flybase took 0.02234935760498047s
Interlinking | Calculation of Degree of Connection for Flybase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Flybase took 6.4849853515625e-05s
Believability | Calculation of trust value for Flybase took 1.2159347534179688e-05s
INFO | --- Analysis for flybase took 7.022184133529663s
Availability | SPARQL endpoint availability check for Flyted took 1.0654032230377197s
Availability | VoID file availability check for Flyted took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Flyted took 0.36165523529052734s
Reputation | Calculation of the PageRank for Flyted took 0.021054744720458984s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0279159545898438e-05s
Believability | Calculation of trust value for Flyted took 1.1205673217773438e-05s
INFO | --- Analysis for flyted took 6.97080135345459s
Availability | SPARQL endpoint availability check for Foodista took 1.7212989330291748s
Availability | VoID file availability check for Foodista took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Foodista took 0.3862278461456299s
Reputation | Calculation of the PageRank for Foodista took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.1948089599609375e-05s
Believability | Calculation of trust value for Foodista took 1.1920928955078125e-05s
INFO | --- Analysis for foodista took 11.723169326782227s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2217245101928711s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.35973501205444336s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02062368392944336s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.271766662597656e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1205673217773438e-05s
INFO | --- Analysis for foodpedia took 3.736860990524292s
Availability | SPARQL endpoint availability check for FrameBase schema took 9.036064147949219e-05s
Availability | VoID file availability check for FrameBase schema took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.38968586921691895s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02207660675048828s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.458427429199219e-05s
Believability | Calculation of trust value for FrameBase schema took 1.049041748046875e-05s
INFO | --- Analysis for framebase-schema took 4.066773891448975s
Availability | SPARQL endpoint availability check for Framester took 8.678436279296875e-05s
Availability | VoID file availability check for Framester took 0.0008106231689453125s
Completeness | Calculation of interlinking completeness for Framester took 0.390636682510376s
Reputation | Calculation of the PageRank for Framester took 0.022753238677978516s
Interlinking | Calculation of Degree of Connection for Framester took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Framester took 7.510185241699219e-05s
Believability | Calculation of trust value for Framester took 1.239776611328125e-05s
INFO | --- Analysis for framester took 5.750809192657471s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.1498274803161621s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.38852572441101074s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020889997482299805s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.463859558105469e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for frb-linked-data took 3.6234891414642334s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 9.107589721679688e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.39296412467956543s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0002639293670654297s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.0728836059570312e-05s
INFO | --- Analysis for freebase took 5.156414270401001s
Availability | SPARQL endpoint availability check for Freeyork took 8.7738037109375e-05s
Availability | VoID file availability check for Freeyork took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Freeyork took 0.3936634063720703s
Reputation | Calculation of the PageRank for Freeyork took 0.022261619567871094s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010848045349121094s
Believability | Calculation of trust value for Freeyork took 5.745887756347656e-05s
INFO | --- Analysis for freeyork-org took 4.177964448928833s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.808624267578125s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.36443495750427246s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020992279052734375s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.486343383789062e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 1.049041748046875e-05s
INFO | --- Analysis for fu-berlin-cordis took 5.924675226211548s
Availability | SPARQL endpoint availability check for DailyMed took 0.7559182643890381s
Availability | VoID file availability check for DailyMed took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for DailyMed took 0.39079976081848145s
Reputation | Calculation of the PageRank for DailyMed took 0.021309375762939453s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.5367431640625e-05s
Believability | Calculation of trust value for DailyMed took 1.33514404296875e-05s
INFO | --- Analysis for fu-berlin-dailymed took 6.884839773178101s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.761693000793457s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.3919031620025635s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.022660493850708008s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.678436279296875e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-dblp took 5.508179664611816s
Availability | SPARQL endpoint availability check for Diseasome took 0.7612674236297607s
Availability | VoID file availability check for Diseasome took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Diseasome took 0.3881216049194336s
Reputation | Calculation of the PageRank for Diseasome took 0.022311687469482422s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010919570922851562s
Believability | Calculation of trust value for Diseasome took 1.0967254638671875e-05s
INFO | --- Analysis for fu-berlin-diseasome took 6.837844133377075s
Availability | SPARQL endpoint availability check for DrugBank took 0.7607264518737793s
Availability | VoID file availability check for DrugBank took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for DrugBank took 0.36812615394592285s
Reputation | Calculation of the PageRank for DrugBank took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.0001285076141357422s
Believability | Calculation of trust value for DrugBank took 1.0251998901367188e-05s
INFO | --- Analysis for fu-berlin-drugbank took 6.859930038452148s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7645683288574219s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.36498379707336426s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.0279159545898438e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 5.527582168579102s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7562658786773682s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.392376184463501s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02103590965270996s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.295608520507812e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 8.821487426757812e-06s
INFO | --- Analysis for fu-berlin-euraxess took 5.514342546463013s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.7663462162017822s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.3879406452178955s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.581710815429688e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-eures took 5.546220779418945s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7657358646392822s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.39154720306396484s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.02265787124633789s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.870529174804688e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 8.821487426757812e-06s
INFO | --- Analysis for fu-berlin-eurostat took 6.204468488693237s
Availability | SPARQL endpoint availability check for MediCare took 0.7666888236999512s
Availability | VoID file availability check for MediCare took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for MediCare took 0.3851592540740967s
Reputation | Calculation of the PageRank for MediCare took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for MediCare took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for MediCare took 3.933906555175781e-05s
Believability | Calculation of trust value for MediCare took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-medicare took 6.163956642150879s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7672967910766602s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.38457751274108887s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.022346973419189453s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.271766662597656e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 5.552875995635986s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7576038837432861s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.3886752128601074s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.226799011230469e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-sider took 6.338163614273071s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7541594505310059s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.36145830154418945s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020830869674682617s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.557868957519531e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-stitch took 5.493757724761963s
Availability | SPARQL endpoint availability check for fvdb took 8.940696716308594e-05s
Availability | VoID file availability check for fvdb took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for fvdb took 0.3605470657348633s
Reputation | Calculation of the PageRank for fvdb took 0.021445512771606445s
Interlinking | Calculation of Degree of Connection for fvdb took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for fvdb took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.6702880859375e-05s
Believability | Calculation of trust value for fvdb took 1.2874603271484375e-05s
INFO | --- Analysis for fv took 13.433857679367065s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 0.00013184547424316406s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.3881552219390869s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.022248506546020508s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.6702880859375e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.0251998901367188e-05s
INFO | --- Analysis for GACS took 4.0802435874938965s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 8.96453857421875e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.39008331298828125s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.814697265625e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.1920928955078125e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 6.273186922073364s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 9.34600830078125e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.38793039321899414s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02158069610595703s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.584426879882812e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.1682510375976562e-05s
INFO | --- Analysis for garnicaplywood took 4.559508323669434s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.654594421386719e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.3914787769317627s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.893013000488281e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.2636184692382812e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 8.937020063400269s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.4071941375732422s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.387631893157959s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 8.821487426757812e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for gemet took 6.187641143798828s
Availability | SPARQL endpoint availability check for gemet-annotated took 9.179115295410156e-05s
Availability | VoID file availability check for gemet-annotated took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.3897712230682373s
Reputation | Calculation of the PageRank for gemet-annotated took 0.0205078125s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.361701965332031e-05s
Believability | Calculation of trust value for gemet-annotated took 1.2636184692382812e-05s
INFO | --- Analysis for gemet-annotated took 4.049973487854004s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.9043631553649902s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.40010786056518555s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.021795034408569336s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.7670135498046875e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.2874603271484375e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 5.370203018188477s
Availability | SPARQL endpoint availability check for Super Ontology took 1.727724313735962s
Availability | VoID file availability check for Super Ontology took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.38657116889953613s
Reputation | Calculation of the PageRank for Super Ontology took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0009403228759765625s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for Super Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 6.109068870544434s
Availability | SPARQL endpoint availability check for Geographic detector model took 5.53131103515625e-05s
Availability | VoID file availability check for Geographic detector model took 0.0004138946533203125s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.39348483085632324s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0009908676147460938s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 4.673004150390625e-05s
Believability | Calculation of trust value for Geographic detector model took 1.2159347534179688e-05s
INFO | --- Analysis for GeoDetector took 20.110447645187378s
Availability | SPARQL endpoint availability check for geodomainwn took 7.891654968261719e-05s
Availability | VoID file availability check for geodomainwn took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.3867826461791992s
Reputation | Calculation of the PageRank for geodomainwn took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.291534423828125e-05s
Believability | Calculation of trust value for geodomainwn took 1.239776611328125e-05s
INFO | --- Analysis for geodomainwn took 8.054676055908203s
Availability | SPARQL endpoint availability check for GeoEcuador took 7.581710815429688e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.3610401153564453s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.461143493652344e-05s
Believability | Calculation of trust value for GeoEcuador took 1.2874603271484375e-05s
INFO | --- Analysis for geoecuador took 13.429983139038086s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.3025667667388916s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.4335510730743408s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.176399230957031e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.2874603271484375e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 49.72137951850891s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5010924339294434s
Availability | VoID file availability check for GeoLinkedData took 0.0011932849884033203s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.3532993793487549s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.021006345748901367s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 9.417533874511719e-05s
Believability | Calculation of trust value for GeoLinkedData took 8.344650268554688e-06s
INFO | --- Analysis for geolinkeddata took 5.006554365158081s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.223344087600708s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.00044035911560058594s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.479241371154785s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.43030643463134766s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.17306137084960938s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.3930845260620117s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.21670913696289062s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.19019460678100586s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.21919012069702148s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.11573314666748047s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.11450433731079102s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.07588386535644531s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.11486244201660156s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.877817153930664s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.11520934104919434s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.12079262733459473s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.15317249298095703s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.11523175239562988s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.07684326171875s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.1152944564819336s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.242368698120117s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 9.632110595703125e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.07660675048828125s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.0775904655456543s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.11514687538146973s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07673931121826172s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.07717347145080566s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.17916274070739746s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.19418931007385254s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.3636276721954346s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 6.20278263092041s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.11465930938720703s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07871437072753906s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07643389701843262s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.352323055267334s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007234334945678711s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22610759735107422s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.07578158378601074s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.2213451862335205s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5285217761993408s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.2937734127044678s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5228729248046875s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.6991033554077148s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.1824967861175537s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07559943199157715s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.1735167503356934s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.3943970203399658s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 5.103443384170532s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 65.10026669502258s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.3392181396484375e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.39060401916503906s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004711151123046875s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.430511474609375e-05s
INFO | --- Analysis for geonames-semantic-web took 4.479430437088013s
Availability | SPARQL endpoint availability check for Geospatial World  took 8.7738037109375e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.3940131664276123s
Reputation | Calculation of the PageRank for Geospatial World  took 0.021681547164916992s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0008969306945800781s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00012087821960449219s
Believability | Calculation of trust value for Geospatial World  took 1.2159347534179688e-05s
INFO | --- Analysis for geospatialworld-net took 4.100600957870483s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.6020972728729248s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.3905632495880127s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020996570587158203s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00014066696166992188s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.3113021850585938e-05s
INFO | --- Analysis for geospecies took 6.930762052536011s
Availability | SPARQL endpoint availability check for GeoWordNet took 9.036064147949219e-05s
Availability | VoID file availability check for GeoWordNet took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.38742661476135254s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02101612091064453s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.245208740234375e-05s
Believability | Calculation of trust value for GeoWordNet took 1.1920928955078125e-05s
INFO | --- Analysis for geowordnet took 8.50049877166748s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.10867524147033691s
Availability | VoID file availability check for German labor law thesaurus took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.36084961891174316s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02242279052734375s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.225440979003906e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 3.5856640338897705s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 9.083747863769531e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.3588745594024658s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02205944061279297s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.482269287109375e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.1444091796875e-05s
INFO | --- Analysis for germlex took 3.8499343395233154s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.4980964660644531s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.3626394271850586s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.021715641021728516s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.512901306152344e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.33514404296875e-05s
INFO | --- Analysis for gesis-thesoz took 6.270917654037476s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.570530652999878s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.3964858055114746s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.772445678710938e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.049041748046875e-05s
INFO | --- Analysis for getty-aat took 17.19991421699524s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.4122538566589355s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.3880035877227783s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.340576171875e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.33514404296875e-05s
INFO | --- Analysis for getty-tgn took 14.395024299621582s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 4.6942198276519775s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.36469483375549316s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 2.956390380859375e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 9.059906005859375e-06s
INFO | --- Analysis for gipuzkoademografia took 28.276024103164673s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 0.00010633468627929688s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.3622715473175049s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02086663246154785s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.075599670410156e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.1920928955078125e-05s
INFO | --- Analysis for glastonbury-2011 took 6.8196940422058105s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.458427429199219e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.3619091510772705s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02215576171875s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.76837158203125e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.239776611328125e-05s
INFO | --- Analysis for global-hunger-index-2011 took 4.2606425285339355s
Availability | SPARQL endpoint availability check for Glottolog took 0.00011110305786132812s
Availability | VoID file availability check for Glottolog took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Glottolog took 0.3882894515991211s
Reputation | Calculation of the PageRank for Glottolog took 0.02197265625s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Glottolog took 6.246566772460938e-05s
Believability | Calculation of trust value for Glottolog took 9.775161743164062e-06s
INFO | --- Analysis for glottolog took 8.263545036315918s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 9.250640869140625e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0009434223175048828s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.36016345024108887s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.021785974502563477s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010704994201660156s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.430511474609375e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 9.826237201690674s
Availability | SPARQL endpoint availability check for 1121 took 4.363059997558594e-05s
Availability | VoID file availability check for 1121 took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for 1121 took 0.38651061058044434s
Reputation | Calculation of the PageRank for 1121 took 0.02201986312866211s
Interlinking | Calculation of Degree of Connection for 1121 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.314018249511719e-05s
Believability | Calculation of trust value for 1121 took 1.239776611328125e-05s
INFO | --- Analysis for God_ took 4.073707342147827s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 9.679794311523438e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.3953745365142822s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.02087092399597168s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0010237693786621094s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 6.0558319091796875e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.239776611328125e-05s
INFO | --- Analysis for gold took 5.244807720184326s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 8.940696716308594e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.3872666358947754s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.794929504394531e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.2159347534179688e-05s
INFO | --- Analysis for googleart-wrapper took 3.854215383529663s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.10696530342102051s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.3964705467224121s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.361701965332031e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.2159347534179688e-05s
INFO | --- Analysis for govagribus-denmark took 36.02018761634827s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.471957206726074s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.3624703884124756s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.678436279296875e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.89917826652527s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.6960039138793945s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.3601846694946289s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020750045776367188s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.202957153320312e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 9.775161743164062e-06s
INFO | --- Analysis for govtrack took 11.772595882415771s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 0.00010323524475097656s
Availability | VoID file availability check for greek-administrative-geography took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.3556499481201172s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.246566772460938e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.2636184692382812e-05s
INFO | --- Analysis for greek-administrative-geography took 3.4125287532806396s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.2182917594909668s
Availability | VoID file availability check for Greek Wordnet took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.3892505168914795s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.022081613540649414s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.220008850097656e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.33514404296875e-05s
INFO | --- Analysis for greek-wordnet took 3.6663424968719482s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.28861546516418457s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007290840148925781s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 13.645043849945068s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.6449081897735596s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.6018021106719971s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.6761095523834229s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.9510893821716309s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5836505889892578s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13957667350769043s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1359245777130127s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13188433647155762s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13334012031555176s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5841929912567139s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13225293159484863s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2500450611114502s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2656865119934082s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13351178169250488s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13651371002197266s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13197112083435059s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.411009788513184s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 6.961822509765625e-05s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13233709335327148s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13035798072814941s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1335735321044922s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13213849067687988s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1334228515625s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.26096463203430176s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.26145076751708984s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 7.724173069000244s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13151001930236816s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.12734103202819824s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.1278209686279297s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.343834161758423s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.2870063781738281s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.59283185005188s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12882423400878906s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.1811697483062744s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 3.2569918632507324s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.279003381729126s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.4150187969207764s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.953090190887451s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12798047065734863s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4994.716996192932s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 5.818532228469849s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021108627319335938s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 3.2901763916015625e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 2.3126602172851562e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 1.430511474609375e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.2874603271484375e-05s
INFO | --- Analysis for greek_prisons_releases took 5080.041000843048s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.8290653228759766s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.36847901344299316s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.058547973632812e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.4781951904296875e-05s
INFO | --- Analysis for greekchildrensartmuseum took 5.65129542350769s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 0.0001049041748046875s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0008361339569091797s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.3866093158721924s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020862340927124023s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010395050048828125s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.2874603271484375e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 8.275675773620605s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.5219032764434814s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.38584017753601074s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020992279052734375s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 6.031990051269531e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.4066696166992188e-05s
INFO | --- Analysis for grrp took 5.095850229263306s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.2747342586517334s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.3605310916900635s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020678281784057617s
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.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.914138793945312e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.9604644775390625e-06s
INFO | --- Analysis for grrt took 4.758827447891235s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1632895469665527s
Availability | VoID file availability check for Geological Timescale took 0.0008008480072021484s
Extra | Recovery of all triples for Geological Timescale took 2.931739091873169s
Performance | Total latancy measurement for Geological Timescale took 4.453912973403931s
Amount of data | Number of triples check for Geological Timescale took 1.057666540145874s
Interoperability | New terms check for Geological Timescale took 2.2443606853485107s
Versatility | Languages check for Geological Timescale took 1.1395862102508545s
Interpretability | Number of blank nodes check for Geological Timescale took 1.0377063751220703s
Security | Check HTTPS for Geological Timescale took 0.9298405647277832s
Interpretability | RDF structures check for Geological Timescale took 1.014345407485962s
Versatility | Serialization formats check for Geological Timescale took 1.018657922744751s
Availability | RDF dump link check for Geological Timescale took 1.8627092838287354s
License | MR license check for Geological Timescale took 1.0002200603485107s
License | HR license check for Geological Timescale took 1.0599110126495361s
Amount of data | Number of property check for Geological Timescale took 1.007411241531372s
Understandability | Number of label check for Geological Timescale took 1.0630662441253662s
Understandability | URI regex check for Geological Timescale took 2.0206310749053955s
Understandability | Vocabs check for Geological Timescale took 1.0249574184417725s
Verifiability | Authors check for Geological Timescale took 1.0426654815673828s
Verifiability | Publishers check for Geological Timescale took 0.4308960437774658s
Performance | Throughput check for Geological Timescale took 13.481138467788696s
Amount of data | Check the number of entities for Geological Timescale took 0.020864486694335938s
Verifiability | Contribs. check for Geological Timescale took 1.0031490325927734s
Interlinking | sameAs chians check for Geological Timescale took 0.44179320335388184s
Interlinking | skos check for Geological Timescale took 1.0020549297332764s
Interlinking | skos check for Geological Timescale took 0.9949235916137695s
Timeliness | dataset update frequency check for Geological Timescale took 1.0227532386779785s
Currency | Creation date check for Geological Timescale took 2.011099100112915s
Currency | Modification date check for Geological Timescale took 1.007990837097168s
Rep.Conc. | URIs length for Geological Timescale took 2.7502307891845703s
Interoperability | New vocabularies check for Geological Timescale took 27.565657377243042s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 1.018340826034546s
Accuracy | Check Functional Property for Geological Timescale took 1.02592134475708s
Accuracy | Check Inverse Functional Property for Geological Timescale took 1.050365686416626s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.3421621322631836s
Accuracy | Check White space in annotation for Geological Timescale took 0.015904903411865234s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07253408432006836s
Consistency | Disjoint class check for Geological Timescale took 0.9976112842559814s
Consistency | Check Misplaced properties for Geological Timescale took 1.475759744644165s
Consistency | Misplaced classes for Geological Timescale took 1.137709140777588s
Consistency | Check Ontology hijacking for Geological Timescale took 1.7784616947174072s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2709290981292725s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.3411386013031006s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05672621726989746s
Conciseness | Check Intensional conciseness for Geological Timescale took 1.0174825191497803s
Security | Sign check for Geological Timescale took 1.0101757049560547s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.45356822013855s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.39034223556518555s
Reputation | Calculation of the PageRank for Geological Timescale took 0.021826505661010742s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 6.985664367675781e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 27.537088871002197s
Believability | Calculation of trust value for Geological Timescale took 1.2636184692382812e-05s
INFO | --- Analysis for GTS took 178.74573850631714s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.36713480949401855s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020890474319458008s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.457069396972656e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for GTS-ont took 3.5079479217529297s
Availability | SPARQL endpoint availability check for GUTSTOK  took 8.940696716308594e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.36610937118530273s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.021008968353271484s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.266334533691406e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.0967254638671875e-05s
INFO | --- Analysis for Guillaume_Forget took 3.3195581436157227s
Availability | SPARQL endpoint availability check for Project Gutenberg took 9.441375732421875e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.39366674423217773s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.021212100982666016s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.295608520507812e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.3589859008789062e-05s
INFO | --- Analysis for gutenberg took 9.920621156692505s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 9.441375732421875e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.3906376361846924s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02096867561340332s
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.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.5762786865234375e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.2636184692382812e-05s
INFO | --- Analysis for gwa-ili took 6.472762584686279s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 9.059906005859375e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.3665580749511719s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 2.956390380859375e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.2636184692382812e-05s
INFO | --- Analysis for GWR took 21.194966793060303s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.315376281738281e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.3628957271575928s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.02205824851989746s
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.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.695487976074219e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.0013580322265625e-05s
INFO | --- Analysis for HASM took 21.235849142074585s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 11.44733476638794s
Availability | VoID file availability check for HealthCare Ontology took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.36193299293518066s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.0209505558013916s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.647804260253906e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for HealthCare_Ontology took 15.379838228225708s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 9.250640869140625e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0009920597076416016s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.3917365074157715s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.021567106246948242s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.103515625e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.0251998901367188e-05s
INFO | --- Analysis for heartfailure took 4.1178271770477295s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.8012433052063s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007724761962890625s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.39734411239624023s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02053213119506836s
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.52587890625e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.600120544433594e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.049041748046875e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 120.58489394187927s
Availability | SPARQL endpoint availability check for Hedatuz took 0.2768895626068115s
Availability | VoID file availability check for Hedatuz took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.3891289234161377s
Reputation | Calculation of the PageRank for Hedatuz took 0.021135330200195312s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.100799560546875e-05s
Believability | Calculation of trust value for Hedatuz took 1.1444091796875e-05s
INFO | --- Analysis for hedatuz took 3.9751217365264893s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.18300485610961914s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.3826563358306885s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012564659118652344s
Believability | Calculation of trust value for Hellenic Fire Brigade took 1.0251998901367188e-05s
INFO | --- Analysis for hellenic-fire-brigade took 3.590317964553833s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.03438425064086914s
Availability | VoID file availability check for Hellenic Police took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.3610219955444336s
Reputation | Calculation of the PageRank for Hellenic Police took 0.021477222442626953s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001342296600341797s
Believability | Calculation of trust value for Hellenic Police took 8.821487426757812e-06s
INFO | --- Analysis for hellenic-police took 3.495049238204956s
Availability | SPARQL endpoint availability check for Hermos took 0.00013327598571777344s
Availability | VoID file availability check for Hermos took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Hermos took 0.381680965423584s
Reputation | Calculation of the PageRank for Hermos took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Hermos took 4.673004150390625e-05s
Believability | Calculation of trust value for Hermos took 1.0967254638671875e-05s
INFO | --- Analysis for Hermos took 3.990424156188965s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 9.322166442871094e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.38563966751098633s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.021346569061279297s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.1948089599609375e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.2874603271484375e-05s
INFO | --- Analysis for Himanshu_Mahawar took 3.41575026512146s
Availability | SPARQL endpoint availability check for HITO took 0.52492356300354s
Availability | VoID file availability check for HITO took 0.0006315708160400391s
Extra | Recovery of all triples for HITO took 1.852339267730713s
Performance | Total latancy measurement for HITO took 0.9931192398071289s
Amount of data | Number of triples check for HITO took 0.20014023780822754s
Interoperability | New terms check for HITO took 1.5133304595947266s
Versatility | Languages check for HITO took 0.22972512245178223s
Interpretability | Number of blank nodes check for HITO took 0.2111835479736328s
Interpretability | RDF structures check for HITO took 0.20440316200256348s
Versatility | Serialization formats check for HITO took 0.20796489715576172s
Availability | RDF dump link check for HITO took 0.2091372013092041s
License | MR license check for HITO took 0.21382927894592285s
License | HR license check for HITO took 0.22882604598999023s
Amount of data | Number of property check for HITO took 0.2072887420654297s
Understandability | Number of label check for HITO took 0.21553921699523926s
Understandability | URI regex check for HITO took 0.4006156921386719s
Understandability | Vocabs check for HITO took 0.20163965225219727s
Verifiability | Authors check for HITO took 0.20532584190368652s
Verifiability | Publishers check for HITO took 0.20143842697143555s
Performance | Throughput check for HITO took 11.120391607284546s
Amount of data | Check the number of entities for HITO took 7.367134094238281e-05s
Verifiability | Contribs. check for HITO took 0.2101728916168213s
Interlinking | sameAs chians check for HITO took 0.20091652870178223s
Interlinking | skos check for HITO took 0.20210790634155273s
Interlinking | skos check for HITO took 0.19431018829345703s
Timeliness | dataset update frequency check for HITO took 0.21207356452941895s
Currency | Creation date check for HITO took 0.39861130714416504s
Currency | Modification date check for HITO took 0.4169459342956543s
Rep.Conc. | URIs length for HITO took 1.1100504398345947s
Interoperability | New vocabularies check for HITO took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.20419836044311523s
Accuracy | Check Functional Property for HITO took 0.20030546188354492s
Accuracy | Check Inverse Functional Property for HITO took 0.20803546905517578s
Accuracy | Check Empty annotation labels for HITO took 0.5378801822662354s
Accuracy | Check White space in annotation for HITO took 0.013495683670043945s
Accuracy | Check Datatype consistency for HITO took 0.07381486892700195s
Consistency | Disjoint class check for HITO took 0.21738886833190918s
Consistency | Check Misplaced properties for HITO took 0.5412061214447021s
Consistency | Misplaced classes for HITO took 0.36998939514160156s
Consistency | Check Ontology hijacking for HITO took 1.771914005279541s
Consistency | Check Invalid usage of undefined classes for HITO took 1.267474889755249s
Consistency | Check Invalid usage of undefined properties for HITO took 1.5497467517852783s
Conciseness | Check Extensional conciseness for HITO took 0.06336092948913574s
Conciseness | Check Intensional conciseness for HITO took 0.20079421997070312s
Security | Sign check for HITO took 0.20437097549438477s
Availability | Check URIs Dereferenciability for HITO took 1942.1806037425995s
Completeness | Calculation of interlinking completeness for HITO took 0.6319425106048584s
Reputation | Calculation of the PageRank for HITO took 0.021183490753173828s
Interlinking | Calculation of Degree of Connection for HITO took 7.939338684082031e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for HITO took 8.0108642578125e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.6689300537109375e-06s
Believability | Calculation of trust value for HITO took 1.2874603271484375e-05s
INFO | --- Analysis for hito took 1996.6313848495483s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 29.91390299797058s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.3643813133239746s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02093052864074707s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.218650817871094e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.1920928955078125e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 97.8674623966217s
Availability | SPARQL endpoint availability check for gseg took 8.940696716308594e-05s
Availability | VoID file availability check for gseg took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for gseg took 0.3602433204650879s
Reputation | Calculation of the PageRank for gseg took 0.021152019500732422s
Interlinking | Calculation of Degree of Connection for gseg took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for gseg took 3.0517578125e-05s
Believability | Calculation of trust value for gseg took 1.4066696166992188e-05s
INFO | --- Analysis for hongse took 4.075575351715088s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 6.128720045089722s
Availability | VoID file availability check for COURAGE Dataset took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.3621861934661865s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.021750926971435547s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0010156631469726562s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 4.5299530029296875e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.4781951904296875e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 11.16167426109314s
Availability | SPARQL endpoint availability check for RoadTrb took 9.608268737792969e-05s
Availability | VoID file availability check for RoadTrb took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.35871338844299316s
Reputation | Calculation of the PageRank for RoadTrb took 0.02101731300354004s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.695487976074219e-05s
Believability | Calculation of trust value for RoadTrb took 1.2636184692382812e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 3.3938815593719482s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 6.151199340820312e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.38773012161254883s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020929813385009766s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 37.52731657028198s
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.0005772113800048828s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.3716754913330078s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.170967102050781e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.3113021850585938e-05s
INFO | --- Analysis for http:pakistan.com took 3.3521251678466797s
Availability | SPARQL endpoint availability check for CEDICT took 9.179115295410156e-05s
Availability | VoID file availability check for CEDICT took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for CEDICT took 0.38990235328674316s
Reputation | Calculation of the PageRank for CEDICT took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.0994415283203125e-05s
Believability | Calculation of trust value for CEDICT took 1.0728836059570312e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.848623037338257s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.663726568222046s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.3609287738800049s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0216677188873291s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.866455078125e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.049041748046875e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 5.848900318145752s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.3903694152832031s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.1682510375976562e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 4.133122682571411s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.601478576660156e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.35650086402893066s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.022221088409423828s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.266334533691406e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.0967254638671875e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 3.3862733840942383s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.839897155761719e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.4071922302246094s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.02121424674987793s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.170967102050781e-05s
Believability | Calculation of trust value for Soccer Dataset took 5.7220458984375e-06s
INFO | --- Analysis for http:www.msm.com took 3.379460096359253s
Availability | SPARQL endpoint availability check for Game Ontology took 7.510185241699219e-05s
Availability | VoID file availability check for Game Ontology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.38842201232910156s
Reputation | Calculation of the PageRank for Game Ontology took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Game Ontology took 1.1444091796875e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 4.101807355880737s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.322166442871094e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.3638451099395752s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021115541458129883s
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.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0013580322265625e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.7960293292999268s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.821487426757812e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.3858754634857178s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0223236083984375s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.049041748046875e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 3.4901959896087646s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.131431579589844e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.4054434299468994s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021862268447875977s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 3.361274003982544s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 7.867813110351562e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3806452751159668s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02195453643798828s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0994415283203125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0013580322265625e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 3.4507923126220703s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.1552734375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.40840888023376465s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021767854690551758s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.504753112792969e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.239776611328125e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 3.4386017322540283s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.916854858398438e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3598756790161133s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0013580322265625e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 4.819223642349243s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.5299530029296875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.38933610916137695s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.123283386230469e-05s
Believability | Calculation of trust value for Indian Biodiversity took 9.775161743164062e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 3.4525742530822754s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 9.179115295410156e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.360994815826416s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.022545337677001953s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.9325485229492188e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.3113021850585938e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 5.740501403808594s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.2579360008239746s
Availability | VoID file availability check for Bookkeeping took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.3923201560974121s
Reputation | Calculation of the PageRank for Bookkeeping took 0.022302865982055664s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.3855438232421875e-05s
Believability | Calculation of trust value for Bookkeeping took 1.3828277587890625e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 5.227111577987671s
Availability | SPARQL endpoint availability check for Legal Ontology took 0.0001266002655029297s
Availability | VoID file availability check for Legal Ontology took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.38941049575805664s
Reputation | Calculation of the PageRank for Legal Ontology took 0.021987199783325195s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 5.1021575927734375e-05s
Believability | Calculation of trust value for Legal Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 4.084535837173462s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.00012636184692382812s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3889737129211426s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02340245246887207s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.96453857421875e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.2636184692382812e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 3.784311532974243s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 9.441375732421875e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.3612399101257324s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.023580074310302734s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 4.982948303222656e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 9.775161743164062e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 3.7075588703155518s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.6685795783996582s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.3939211368560791s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.021727561950683594s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010919570922851562s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 9.775161743164062e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 3.942652702331543s
Availability | SPARQL endpoint availability check for IATE RDF took 0.00011372566223144531s
Availability | VoID file availability check for IATE RDF took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.3589153289794922s
Reputation | Calculation of the PageRank for IATE RDF took 0.021087169647216797s
Interlinking | Calculation of Degree of Connection for IATE RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for IATE RDF took 1.1920928955078125e-05s
INFO | --- Analysis for iate-rdf took 3.740640163421631s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.434464693069458s
Availability | VoID file availability check for IATI as Linked Data took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.3624591827392578s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.416175842285156e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for iati-as-linked-data took 15.137575387954712s
Availability | SPARQL endpoint availability check for ICANE took 0.3391146659851074s
Availability | VoID file availability check for ICANE took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for ICANE took 0.3904001712799072s
Reputation | Calculation of the PageRank for ICANE took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for ICANE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICANE took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.7738037109375e-05s
Believability | Calculation of trust value for ICANE took 8.58306884765625e-06s
INFO | --- Analysis for icane took 4.525621652603149s
Availability | SPARQL endpoint availability check for ichoose took 0.1692638397216797s
Availability | VoID file availability check for ichoose took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for ichoose took 0.519073486328125s
Reputation | Calculation of the PageRank for ichoose took 0.021121978759765625s
Interlinking | Calculation of Degree of Connection for ichoose took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.176399230957031e-05s
Believability | Calculation of trust value for ichoose took 9.775161743164062e-06s
INFO | --- Analysis for ichoose took 45.76127314567566s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 1.3330907821655273s
Availability | VoID file availability check for The Iconology Dataset took 0.0005393028259277344s
Extra | Recovery of all triples for The Iconology Dataset took 3.4348528385162354s
Performance | Total latancy measurement for The Iconology Dataset took 0.5225975513458252s
Amount of data | Number of triples check for The Iconology Dataset took 0.26384973526000977s
Interoperability | New terms check for The Iconology Dataset took 1.3988614082336426s
Versatility | Languages check for The Iconology Dataset took 0.6340999603271484s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.1952216625213623s
Interpretability | RDF structures check for The Iconology Dataset took 0.14686322212219238s
Versatility | Serialization formats check for The Iconology Dataset took 0.12172389030456543s
Availability | RDF dump link check for The Iconology Dataset took 0.10457611083984375s
License | MR license check for The Iconology Dataset took 0.11985492706298828s
License | HR license check for The Iconology Dataset took 0.28301191329956055s
Amount of data | Number of property check for The Iconology Dataset took 0.1091008186340332s
Understandability | Number of label check for The Iconology Dataset took 0.15713858604431152s
Understandability | URI regex check for The Iconology Dataset took 0.1784954071044922s
Understandability | Vocabs check for The Iconology Dataset took 0.0905771255493164s
Verifiability | Authors check for The Iconology Dataset took 0.10146188735961914s
Verifiability | Publishers check for The Iconology Dataset took 0.09831452369689941s
Performance | Throughput check for The Iconology Dataset took 10.619606971740723s
Amount of data | Check the number of entities for The Iconology Dataset took 9.441375732421875e-05s
Verifiability | Contribs. check for The Iconology Dataset took 0.09291434288024902s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09999418258666992s
Interlinking | skos check for The Iconology Dataset took 0.09265017509460449s
Interlinking | skos check for The Iconology Dataset took 0.09284639358520508s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09220099449157715s
Currency | Creation date check for The Iconology Dataset took 0.1867961883544922s
Currency | Modification date check for The Iconology Dataset took 0.18474149703979492s
Rep.Conc. | URIs length for The Iconology Dataset took 1.337641954421997s
Interoperability | New vocabularies check for The Iconology Dataset took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08240318298339844s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.24928832054138184s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016419410705566406s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.41843247413635254s
Consistency | Disjoint class check for The Iconology Dataset took 0.08420085906982422s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.14984464645385742s
Consistency | Misplaced classes for The Iconology Dataset took 0.8485186100006104s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.558279037475586s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.23976469039917s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.3144769668579102s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2994980812072754s
Security | Sign check for The Iconology Dataset took 0.08364462852478027s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2978.677211523056s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.839545726776123s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.021341323852539062s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.288818359375e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for The Iconology Dataset took 1.3589859008789062e-05s
INFO | --- Analysis for iconology-dataset took 3037.1475892066956s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.4345855712890625e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.360095739364624s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.677078247070312e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.239776611328125e-05s
INFO | --- Analysis for idreffr took 4.8444249629974365s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.7726848125457764s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.36138248443603516s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0009396076202392578s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 6.461143493652344e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.239776611328125e-05s
INFO | --- Analysis for ids took 4.789614915847778s
Availability | SPARQL endpoint availability check for ietflang took 8.916854858398438e-05s
Availability | VoID file availability check for ietflang took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for ietflang took 0.36395764350891113s
Reputation | Calculation of the PageRank for ietflang took 0.021126747131347656s
Interlinking | Calculation of Degree of Connection for ietflang took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.57763671875e-05s
Believability | Calculation of trust value for ietflang took 1.0967254638671875e-05s
INFO | --- Analysis for ietflang took 15.248807191848755s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.7493441104888916s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.39070963859558105s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02101278305053711s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for IGVLL took 5.298710823059082s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.48938441276550293s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0005540847778320312s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.421828269958496s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 1.0105152130126953s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.20209431648254395s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.449707269668579s
Versatility | Languages check for 3LGM² IHE Ontology took 0.24871516227722168s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.2057638168334961s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.26560449600219727s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.21063232421875s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.19991493225097656s
License | MR license check for 3LGM² IHE Ontology took 0.2133955955505371s
License | HR license check for 3LGM² IHE Ontology took 0.20987963676452637s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.2080068588256836s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.21966338157653809s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.4051327705383301s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.20335721969604492s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.19845342636108398s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.20116662979125977s
Performance | Throughput check for 3LGM² IHE Ontology took 11.548936605453491s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.510185241699219e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.2022993564605713s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.20952510833740234s
Interlinking | skos check for 3LGM² IHE Ontology took 0.19344210624694824s
Interlinking | skos check for 3LGM² IHE Ontology took 0.19595980644226074s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.20287847518920898s
Currency | Creation date check for 3LGM² IHE Ontology took 0.3960297107696533s
Currency | Modification date check for 3LGM² IHE Ontology took 0.404559850692749s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8336880207061768s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.19399380683898926s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.20739412307739258s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.1981499195098877s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.36971044540405273s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0016143321990966797s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.04934120178222656s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.20758295059204102s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4571347236633301s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.29200053215026855s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.563086986541748s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.2356576919555664s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.5087766647338867s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03128170967102051s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.21048498153686523s
Security | Sign check for 3LGM² IHE Ontology took 0.20196032524108887s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 394.58133840560913s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.5154135227203369s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.021111011505126953s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 4.1484832763671875e-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 1.430511474609375e-05s
INFO | --- Analysis for IHE took 443.0422513484955s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.4413483142852783s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0007352828979492188s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 6.668022155761719s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 7.4282097816467285s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 20.068938732147217s
Interoperability | New terms check for Test Site, LOD Lab 317 took 7.431391954421997s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.49525785446167s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.838304042816162s
Security | Check HTTPS for Test Site, LOD Lab 317 took 0.9923224449157715s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.6173715591430664s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.5767624378204346s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.4840118885040283s
License | MR license check for Test Site, LOD Lab 317 took 1.5812416076660156s
License | HR license check for Test Site, LOD Lab 317 took 1.8618755340576172s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.5353124141693115s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.7049353122711182s
Understandability | URI regex check for Test Site, LOD Lab 317 took 2.996514081954956s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.5068559646606445s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.5432074069976807s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.4961912631988525s
Performance | Throughput check for Test Site, LOD Lab 317 took 14.855510711669922s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 7.05718994140625e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.5023424625396729s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.4995765686035156s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.5449554920196533s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.516519546508789s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.5397820472717285s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.0174927711486816s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.0052969455718994s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 34.72424006462097s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.4938502311706543s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.524782657623291s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.5268261432647705s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 2.9287190437316895s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.031568288803100586s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.028464555740356445s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.4961116313934326s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 26.259133338928223s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 1.8326303958892822s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 7.150757312774658s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.2301576137542725s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 23.04002547264099s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.03302764892578125s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.078730821609497s
Security | Sign check for Test Site, LOD Lab 317 took 1.5530564785003662s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 9.90743637084961s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.41463303565979004s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021050214767456055s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 7.367134094238281e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.430511474609375e-05s
INFO | --- Analysis for iislod-test took 556.1352183818817s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 9.465217590332031e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.001043081283569336s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.39140844345092773s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.147125244140625e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.0251998901367188e-05s
INFO | --- Analysis for ILUSOC took 19.624723196029663s
Availability | SPARQL endpoint availability check for im@sparql took 7.22846245765686s
Availability | VoID file availability check for im@sparql took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for im@sparql took 0.3868520259857178s
Reputation | Calculation of the PageRank for im@sparql took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.123283386230469e-05s
Believability | Calculation of trust value for im@sparql took 1.049041748046875e-05s
INFO | --- Analysis for im@sparql took 15.555066108703613s
Availability | SPARQL endpoint availability check for imagery bailingniao took 9.083747863769531e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.3939054012298584s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.022335052490234375s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.1948089599609375e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.1920928955078125e-05s
INFO | --- Analysis for imagery_bailingniao took 4.623129367828369s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1641578674316406s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006184577941894531s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 20.829360246658325s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.677133321762085s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.926566123962402s
Interoperability | New terms check for Imagesnippets Image Descriptions took 2.251697540283203s
Versatility | Languages check for Imagesnippets Image Descriptions took 21.295739889144897s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.46121621131897s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7389826774597168s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7773747444152832s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7753708362579346s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7628238201141357s
License | MR license check for Imagesnippets Image Descriptions took 0.7688350677490234s
License | HR license check for Imagesnippets Image Descriptions took 30.7664635181427s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7718894481658936s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.684349298477173s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.5306482315063477s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7617816925048828s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7627322673797607s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7629711627960205s
Performance | Throughput check for Imagesnippets Image Descriptions took 14.683513164520264s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 0.00010442733764648438s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7677872180938721s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 1.0150206089019775s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7752678394317627s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7352802753448486s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7649893760681152s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.5421781539916992s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.5333633422851562s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.526296854019165s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.770341157913208s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7609333992004395s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7604765892028809s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 11.444974899291992s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2096502780914307s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.191477537155151s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7961390018463135s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 8.349486827850342s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.269068956375122s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.439375638961792s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 9.080957412719727s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.9462509155273438s
Security | Sign check for Imagesnippets Image Descriptions took 0.7786707878112793s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 15.533211946487427s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.44750285148620605s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.942054748535156e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.6689300537109375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 6.67572021484375e-06s
INFO | --- Analysis for imagesnippets took 389.0552382469177s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.23284006118774414s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.3616766929626465s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.5367431640625e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 7.62939453125e-06s
INFO | --- Analysis for imf-linked-data took 3.65753173828125s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.792213439941406e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.38529229164123535s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1682510375976562e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.1444091796875e-05s
INFO | --- Analysis for Imtiaz took 3.4416873455047607s
Availability | SPARQL endpoint availability check for Royalty Free Music took 7.605552673339844e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.3857300281524658s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.9087066650390625e-05s
Believability | Calculation of trust value for Royalty Free Music took 1.1205673217773438e-05s
INFO | --- Analysis for inaudio.org took 4.893445253372192s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.5832464694976807s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.3864262104034424s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.022129058837890625s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 5.082507371902466s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 8.7738037109375e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.36408138275146484s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.021023273468017578s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010466575622558594s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.239776611328125e-05s
INFO | --- Analysis for ineverycrea took 14.295692205429077s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.083747863769531e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007708072662353516s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.36960434913635254s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.023108243942260742s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0009737014770507812s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00011110305786132812s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.2159347534179688e-05s
INFO | --- Analysis for ineverycrea-argentina took 8.805456161499023s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 270.87682843208313s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.4858286380767822s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 8.368492126464844e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for influence-tracker-dataset took 566.7245290279388s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.482269287109375e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.38745760917663574s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.02307271957397461s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.314018249511719e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 8.821487426757812e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 3.4436163902282715s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.012222290039062e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.5183179378509521s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.021058082580566406s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.512901306152344e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for interactivemaps-gnoss took 9.40514588356018s
Availability | SPARQL endpoint availability check for intervalue took 0.28183746337890625s
Availability | VoID file availability check for intervalue took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for intervalue took 0.3599872589111328s
Reputation | Calculation of the PageRank for intervalue took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.818771362304688e-05s
Believability | Calculation of trust value for intervalue took 1.1682510375976562e-05s
INFO | --- Analysis for intervalue took 3.682920217514038s
Availability | SPARQL endpoint availability check for Inztrow took 5.221366882324219e-05s
Availability | VoID file availability check for Inztrow took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Inztrow took 0.3919832706451416s
Reputation | Calculation of the PageRank for Inztrow took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.0994415283203125e-05s
Believability | Calculation of trust value for Inztrow took 1.049041748046875e-05s
INFO | --- Analysis for Inztrow took 5.127282381057739s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.3851966857910156s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.02075791358947754s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for ipbes took 4.7316670417785645s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 7.462501525878906e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0003609657287597656s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.38868165016174316s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.506111145019531e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.3113021850585938e-05s
INFO | --- Analysis for iptc-newscodes took 5.025362014770508s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.5285422801971436s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0003578662872314453s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.3949124813079834s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.00011420249938964844s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.867813110351562e-06s
INFO | --- Analysis for iserve took 10.385684967041016s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.95152997970581s
Availability | VoID file availability check for ISIC V4 took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.36444902420043945s
Reputation | Calculation of the PageRank for ISIC V4 took 0.021005630493164062s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.291534423828125e-05s
Believability | Calculation of trust value for ISIC V4 took 6.198883056640625e-06s
INFO | --- Analysis for isic-v4 took 115.68329668045044s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.4345855712890625e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.3878464698791504s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 6.914138793945312e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 4.291534423828125e-06s
INFO | --- Analysis for isil-dbpedia took 5.368968725204468s
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.00041294097900390625s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.37821221351623535s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.600120544433594e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 7.867813110351562e-06s
INFO | --- Analysis for iso-639-oasis took 4.2384703159332275s
Availability | SPARQL endpoint availability check for ISOcat took 4.363059997558594e-05s
Availability | VoID file availability check for ISOcat took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for ISOcat took 0.35991883277893066s
Reputation | Calculation of the PageRank for ISOcat took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for ISOcat took 5.984306335449219e-05s
Believability | Calculation of trust value for ISOcat took 1.2874603271484375e-05s
INFO | --- Analysis for isocat took 8.798680543899536s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 0.00011086463928222656s
Availability | VoID file availability check for ISOcat-metadata took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.39084935188293457s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020827054977416992s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.62396240234375e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.3113021850585938e-05s
INFO | --- Analysis for isocat-metadata took 6.072795152664185s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2532474994659424s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006129741668701172s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.539211273193359s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5462381839752197s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20537614822387695s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.933147430419922s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.80676603317261s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1381380558013916s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.06382131576538086s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1553516387939453s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16341018676757812s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.141937255859375s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18735265731811523s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 92.09674739837646s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1408536434173584s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4863002300262451s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.38147854804992676s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17517638206481934s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1812424659729004s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13904976844787598s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.543755292892456s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.200241088867188e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17384719848632812s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.23276782035827637s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4210083484649658s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3835937976837158s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1796128749847412s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5372085571289062s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14539051055908203s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.242351770401001s
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.13772344589233398s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14160585403442383s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1499941349029541s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8469009399414062s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3089332580566406s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2688603401184082s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13744902610778809s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.281597137451172s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9578750133514404s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.9265871047973633s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3006782531738281s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.101982831954956s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3035867214202881s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15965008735656738s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15231823921203613s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.507272243499756s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4215099811553955s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.021209716796875s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.489059448242188e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.9073486328125e-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 453.6992292404175s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.10613250732421875s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0005824565887451172s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.483076572418213s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.5377178192138672s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.20027613639831543s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.934723377227783s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 91.24728894233704s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.13872504234313965s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.06379055976867676s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.15438556671142578s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.1643354892730713s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.14074444770812988s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.1860055923461914s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.95084834098816s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.1428661346435547s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.237205982208252s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.39013099670410156s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.17479968070983887s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.17925739288330078s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.33266425132751465s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.499975681304932s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.152557373046875e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.17387676239013672s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.22923994064331055s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.41042232513427734s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.37749648094177246s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.17723369598388672s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.2801845073699951s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.14521408081054688s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 13.137418270111084s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.13538837432861328s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.14000654220581055s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.14014649391174316s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.9278342723846436s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3089158535003662s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.26936936378479004s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.13787150382995605s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.298572301864624s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9470388889312744s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 3.1743435859680176s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.2635583877563477s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.134706974029541s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.30664753913879395s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.15562653541564941s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.3303639888763428s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 9.688250303268433s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.5348958969116211s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.02094292640686035s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.1682510375976562e-05s
INFO | --- Analysis for ispra-lod-ron took 453.054105758667s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.8163661956787109s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.00039005279541015625s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.3997218608856201s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.608268737792969e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 7.62939453125e-06s
INFO | --- Analysis for issa-agritrop took 6.067378044128418s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.38690185546875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.35273122787475586s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.9325485229492188e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 8.106231689453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 3.321458101272583s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.5299530029296875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.359144926071167s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.8848648071289062e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.152557373046875e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 3.727149724960327s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 5.626678466796875e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.38566112518310547s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 2.9087066650390625e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 7.62939453125e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 3.6156938076019287s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.5870766639709473s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.353395938873291s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.749961853027344e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 9.5367431640625e-06s
INFO | --- Analysis for istat-immigration took 5.0048675537109375s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.26596665382385254s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.3810384273529053s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.8848648071289062e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 5.0067901611328125e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.8546130657196045s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.2701237201690674s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.3805215358734131s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 8.368492126464844e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 7.867813110351562e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 4.644040822982788s
Availability | SPARQL endpoint availability check for IWN took 4.3392181396484375e-05s
Availability | VoID file availability check for IWN took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for IWN took 0.33290576934814453s
Reputation | Calculation of the PageRank for IWN took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for IWN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for IWN took 3.4809112548828125e-05s
Believability | Calculation of trust value for IWN took 7.867813110351562e-06s
INFO | --- Analysis for iwn took 6.979621648788452s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.764227390289307s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.3609037399291992s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.008148193359375e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 8.106231689453125e-06s
INFO | --- Analysis for jamendo-dbtune took 11.450165510177612s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.363059997558594e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.3593447208404541s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.601478576660156e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for japan-radioactivity-stat took 6.023191928863525s
Availability | SPARQL endpoint availability check for JEL Classification took 5.078315734863281e-05s
Availability | VoID file availability check for JEL Classification took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.3280172348022461s
Reputation | Calculation of the PageRank for JEL Classification took 0.02115797996520996s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.9087066650390625e-05s
Believability | Calculation of trust value for JEL Classification took 8.106231689453125e-06s
INFO | --- Analysis for jel-classification took 5.972386121749878s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.2166800498962402s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.33815598487854004s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020925283432006836s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 7.62939453125e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.8627753257751465s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.6743667125702s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.3369266986846924s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.022292375564575195s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.749961853027344e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.0728836059570312e-05s
INFO | --- Analysis for jita took 542.7298848628998s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.089722156524658s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.3131532669067383s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02177143096923828s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.751319885253906e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.3828277587890625e-05s
INFO | --- Analysis for john-goodwins-family-tree took 63.573816537857056s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 9.1552734375e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.33919620513916016s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02214217185974121s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.4332275390625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.1920928955078125e-05s
INFO | --- Analysis for jp-cos took 5.487378358840942s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.291534423828125e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0008244514465332031s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.3391401767730713s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.00543212890625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.2159347534179688e-05s
INFO | --- Analysis for jp-textbook took 4.960925579071045s
Availability | SPARQL endpoint availability check for JRC-Names took 4.863739013671875e-05s
Availability | VoID file availability check for JRC-Names took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.3473789691925049s
Reputation | Calculation of the PageRank for JRC-Names took 0.021553754806518555s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 4.00543212890625e-05s
Believability | Calculation of trust value for JRC-Names took 1.3589859008789062e-05s
INFO | --- Analysis for jrc-names-ec took 5.295806407928467s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.0132358074188232s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.33727145195007324s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.022802352905273438s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.937980651855469e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.1920928955078125e-05s
INFO | --- Analysis for jrc-names-mlode took 4.124218702316284s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.410743713378906e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.31525397300720215s
Reputation | Calculation of the PageRank for JudaicaLink took 0.023298025131225586s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 9.942054748535156e-05s
Believability | Calculation of trust value for JudaicaLink took 1.1444091796875e-05s
INFO | --- Analysis for judaicalink took 5.027306318283081s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07445979118347168s
Availability | VoID file availability check for Kallikratis municipalities took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.3381307125091553s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.274482727050781e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 1.0251998901367188e-05s
INFO | --- Analysis for kallikratis-municipalities took 3.0746243000030518s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.5299530029296875e-05s
Availability | VoID file availability check for EU Soccer League took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.3095879554748535s
Reputation | Calculation of the PageRank for EU Soccer League took 0.022864103317260742s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.0517578125e-05s
Believability | Calculation of trust value for EU Soccer League took 1.049041748046875e-05s
INFO | --- Analysis for KG:Course_Submission took 5.102349042892456s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.4345855712890625e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.3387479782104492s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.021060943603515625s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.239776611328125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.0967254638671875e-05s
INFO | --- Analysis for KING took 3.195828676223755s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 9.34600830078125e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.3146641254425049s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.604194641113281e-05s
Believability | Calculation of trust value for Klappstuhlclub took 7.867813110351562e-06s
INFO | --- Analysis for klappstuhlclub took 13.094320058822632s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.939282894134521s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.3155553340911865s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.021053075790405273s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.079673767089844e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.3113021850585938e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.931941509246826s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.792213439941406e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.3083302974700928s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.022423505783081055s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.0040740966796875e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.2874603271484375e-05s
INFO | --- Analysis for KnowledgeFusion took 2.8163957595825195s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 9.059906005859375e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.320997953414917s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.318092346191406e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.1920928955078125e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.792397022247314s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.5367431640625e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.3193485736846924s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.6702880859375e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.33514404296875e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.9316046237945557s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.38690185546875e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.3123335838317871s
Reputation | Calculation of the PageRank for Informatics Studies took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.9087066650390625e-05s
Believability | Calculation of trust value for Informatics Studies took 1.0967254638671875e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.662851095199585s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.0906684398651123s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.33484721183776855s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.743171691894531e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.3589859008789062e-05s
INFO | --- Analysis for kupkb took 10.832672834396362s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 9.752505540847778s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.33754777908325195s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.177757263183594e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.049041748046875e-05s
INFO | --- Analysis for l3s-dblp took 44.22876191139221s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 22.70344853401184s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.3152778148651123s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.699562072753906e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.33514404296875e-05s
INFO | --- Analysis for lak-dataset took 66.3258068561554s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.21126389503479004s
Availability | VoID file availability check for  Language Name Authority List  took 0.0006167888641357422s
Extra | Recovery of all triples for  Language Name Authority List  took 163.75462818145752s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6013405323028564s
Amount of data | Number of triples check for  Language Name Authority List  took 174.46297550201416s
Interoperability | New terms check for  Language Name Authority List  took 58.50190043449402s
Versatility | Languages check for  Language Name Authority List  took 300.07537603378296s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 16.22445821762085s
Security | Check HTTPS for  Language Name Authority List  took 0.37518906593322754s
Interpretability | RDF structures check for  Language Name Authority List  took 0.5934524536132812s
Versatility | Serialization formats check for  Language Name Authority List  took 3.7961196899414062s
Availability | RDF dump link check for  Language Name Authority List  took 0.21677327156066895s
License | MR license check for  Language Name Authority List  took 0.4513368606567383s
License | HR license check for  Language Name Authority List  took 300.03744435310364s
Amount of data | Number of property check for  Language Name Authority List  took 0.218766450881958s
Understandability | Number of label check for  Language Name Authority List  took 2.7383837699890137s
Understandability | URI regex check for  Language Name Authority List  took 0.36893558502197266s
Understandability | Vocabs check for  Language Name Authority List  took 0.12178993225097656s
Verifiability | Authors check for  Language Name Authority List  took 0.2212677001953125s
Verifiability | Publishers check for  Language Name Authority List  took 0.272705078125s
Performance | Throughput check for  Language Name Authority List  took 10.581201553344727s
Amount of data | Check the number of entities for  Language Name Authority List  took 7.867813110351562e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.15245771408081055s
Interlinking | sameAs chians check for  Language Name Authority List  took 7.033817291259766s
Interlinking | skos check for  Language Name Authority List  took 0.16762471199035645s
Interlinking | skos check for  Language Name Authority List  took 0.3202080726623535s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.3027002811431885s
Currency | Creation date check for  Language Name Authority List  took 0.28615760803222656s
Currency | Modification date check for  Language Name Authority List  took 0.15291428565979004s
Rep.Conc. | URIs length for  Language Name Authority List  took 407.2769730091095s
Interoperability | New vocabularies check for  Language Name Authority List  took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.16927123069763184s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.2049236297607422s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.41808485984802246s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.8879120349884s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.1673190593719482s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.607361078262329s
Consistency | Disjoint class check for  Language Name Authority List  took 0.15018773078918457s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.4506115913391s
Consistency | Misplaced classes for  Language Name Authority List  took 8.445511817932129s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 39.62920594215393s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.659942388534546s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.4883906841278s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.1614532470703125s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.5188915729522705s
Security | Sign check for  Language Name Authority List  took 0.5699081420898438s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 11.431720972061157s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.7808644771575928s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.029114246368408203s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 6.628036499023438e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.703636169433594e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.6689300537109375e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.2636184692382812e-05s
INFO | --- Analysis for language-authority-list took 15998.524609804153s
Availability | SPARQL endpoint availability check for Lark took 384.24105954170227s
Availability | VoID file availability check for Lark took 0.0008852481842041016s
Completeness | Calculation of interlinking completeness for Lark took 0.6081681251525879s
Reputation | Calculation of the PageRank for Lark took 0.021058320999145508s
Interlinking | Calculation of Degree of Connection for Lark took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Lark took 7.677078247070312e-05s
Believability | Calculation of trust value for Lark took 1.3589859008789062e-05s
INFO | --- Analysis for LARK took 1676.2403569221497s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.6150519847869873s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.37933850288391113s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for LASLA took 4.841235876083374s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.5925707817077637s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.3397796154022217s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 5.1021575927734375e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 4.70835280418396s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.58711838722229s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.3097879886627197s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.021687984466552734s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for LatinAffectus took 4.7754669189453125s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.5623061656951904s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.31036972999572754s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.02092766761779785s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.38690185546875e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for LatinWordnetLiLa took 4.885149717330933s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.76837158203125e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.34364891052246094s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02126002311706543s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00012087821960449219s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.0251998901367188e-05s
INFO | --- Analysis for lcsh took 7.389923572540283s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.744529724121094e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.3109285831451416s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02118968963623047s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.726119995117188e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.239776611328125e-05s
INFO | --- Analysis for lcsubjects took 3.1168978214263916s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.58053207397461s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0007898807525634766s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.38590049743652344s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02102375030517578s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.267692565917969e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.239776611328125e-05s
INFO | --- Analysis for ldt@library took 36.570194482803345s
Availability | SPARQL endpoint availability check for U ime Legije took 9.5367431640625e-05s
Availability | VoID file availability check for U ime Legije took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.3475167751312256s
Reputation | Calculation of the PageRank for U ime Legije took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.552436828613281e-05s
Believability | Calculation of trust value for U ime Legije took 3.314018249511719e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 3.0257186889648438s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.5652530193328857s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.3135719299316406s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.128715515136719e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.2874603271484375e-05s
INFO | --- Analysis for LemmaBank took 5.255022764205933s
Availability | SPARQL endpoint availability check for lemonUby took 4.887580871582031e-05s
Availability | VoID file availability check for lemonUby took 0.0004127025604248047s
Completeness | Calculation of interlinking completeness for lemonUby took 0.3109140396118164s
Reputation | Calculation of the PageRank for lemonUby took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.246566772460938e-05s
Believability | Calculation of trust value for lemonUby took 1.1682510375976562e-05s
INFO | --- Analysis for lemonuby took 3.7627577781677246s
Availability | SPARQL endpoint availability check for LemonWiktionary took 9.036064147949219e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.34618377685546875s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.021647214889526367s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.62396240234375e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.2636184692382812e-05s
INFO | --- Analysis for lemonwiktionary took 4.865113973617554s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.5595734119415283s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.33892011642456055s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02326369285583496s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for LewisShort took 4.653425216674805s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.12168550491333s
Availability | VoID file availability check for LEXIN-RDF took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.3350718021392822s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020929574966430664s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.1948089599609375e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.1682510375976562e-05s
INFO | --- Analysis for lexin-rdf took 6.390614032745361s
Availability | SPARQL endpoint availability check for lexinfo took 8.916854858398438e-05s
Availability | VoID file availability check for lexinfo took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for lexinfo took 0.31092190742492676s
Reputation | Calculation of the PageRank for lexinfo took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.940696716308594e-05s
Believability | Calculation of trust value for lexinfo took 1.4066696166992188e-05s
INFO | --- Analysis for lexinfo took 3.4565091133117676s
Availability | SPARQL endpoint availability check for Lexvo took 4.506111145019531e-05s
Availability | VoID file availability check for Lexvo took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Lexvo took 0.33701658248901367s
Reputation | Calculation of the PageRank for Lexvo took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.0001766681671142578s
Believability | Calculation of trust value for Lexvo took 1.2159347534179688e-05s
INFO | --- Analysis for lexvo took 3.5670056343078613s
Availability | SPARQL endpoint availability check for Lexvo.org took 9.894371032714844e-05s
Availability | VoID file availability check for Lexvo.org took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.30924510955810547s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.390975952148438e-05s
Believability | Calculation of trust value for Lexvo.org took 1.239776611328125e-05s
INFO | --- Analysis for lexvo-org took 3.0028767585754395s
Availability | SPARQL endpoint availability check for LIBRIS took 0.41843414306640625s
Availability | VoID file availability check for LIBRIS took 0.0006144046783447266s
Extra | Recovery of all triples for LIBRIS took 6.569857120513916s
Performance | Total latancy measurement for LIBRIS took 0.7753887176513672s
Amount of data | Number of triples check for LIBRIS took 25.803524017333984s
Interoperability | New terms check for LIBRIS took 15.34846806526184s
Versatility | Languages check for LIBRIS took 0.21260666847229004s
Interpretability | Number of blank nodes check for LIBRIS took 300.103080034256s
Security | Check HTTPS for LIBRIS took 0.36438941955566406s
Interpretability | RDF structures check for LIBRIS took 0.3058891296386719s
Versatility | Serialization formats check for LIBRIS took 0.226240873336792s
Availability | RDF dump link check for LIBRIS took 0.14221954345703125s
License | MR license check for LIBRIS took 0.20699572563171387s
License | HR license check for LIBRIS took 0.17485475540161133s
Amount of data | Number of property check for LIBRIS took 0.21360421180725098s
Understandability | Number of label check for LIBRIS took 0.3442964553833008s
Understandability | URI regex check for LIBRIS took 0.3097081184387207s
Understandability | Vocabs check for LIBRIS took 0.14376235008239746s
Verifiability | Authors check for LIBRIS took 0.147660493850708s
Verifiability | Publishers check for LIBRIS took 0.14317107200622559s
Performance | Throughput check for LIBRIS took 11.19355320930481s
Amount of data | Check the number of entities for LIBRIS took 0.0001556873321533203s
Verifiability | Contribs. check for LIBRIS took 0.16882681846618652s
Interlinking | sameAs chians check for LIBRIS took 0.14545059204101562s
Interlinking | skos check for LIBRIS took 0.2667875289916992s
Interlinking | skos check for LIBRIS took 0.1428697109222412s
Timeliness | dataset update frequency check for LIBRIS took 0.14569473266601562s
Currency | Creation date check for LIBRIS took 0.35297727584838867s
Currency | Modification date check for LIBRIS took 0.6672177314758301s
Rep.Conc. | URIs length for LIBRIS took 76.99400663375854s
Interoperability | New vocabularies check for LIBRIS took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.2143239974975586s
Accuracy | Check Functional Property for LIBRIS took 0.21044659614562988s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.2313385009765625s
Accuracy | Check Datatype consistency for LIBRIS took 0.26981282234191895s
Consistency | Disjoint class check for LIBRIS took 0.20908832550048828s
Consistency | Check Misplaced properties for LIBRIS took 59.34996461868286s
Consistency | Misplaced classes for LIBRIS took 1.1488134860992432s
Consistency | Check Ontology hijacking for LIBRIS took 3.4540698528289795s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.2843303680419922s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 60.28206181526184s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2888336181640625s
Conciseness | Check Intensional conciseness for LIBRIS took 0.436084508895874s
Security | Sign check for LIBRIS took 0.23584699630737305s
Availability | Check URIs Dereferenciability for LIBRIS took 9.382730722427368s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.4600489139556885s
Reputation | Calculation of the PageRank for LIBRIS took 0.020388126373291016s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00015163421630859375s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.6689300537109375e-06s
Believability | Calculation of trust value for LIBRIS took 1.049041748046875e-05s
INFO | --- Analysis for libris took 1117.9730806350708s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.07639694213867188s
Availability | VoID file availability check for Public Library of Veroia took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.3148989677429199s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02195596694946289s
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.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.677078247070312e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.33514404296875e-05s
INFO | --- Analysis for libver took 4.220914363861084s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.15126347541809082s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.33921217918395996s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02112102508544922s
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.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.273124694824219e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 1.0013580322265625e-05s
INFO | --- Analysis for lichfield-spending took 3.1383461952209473s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 9.1552734375e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.31217241287231445s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.021878719329833984s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.409385681152344e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.3589859008789062e-05s
INFO | --- Analysis for lime took 7.301109075546265s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 8.988380432128906e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.46095967292785645s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.3097870349884033s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.022126436233520508s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0009372234344482422s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00012969970703125s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.3828277587890625e-05s
INFO | --- Analysis for lingvoj took 10.043869495391846s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 8.0108642578125e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.311586856842041s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.796287536621094e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.2874603271484375e-05s
INFO | --- Analysis for linked-crunchbase took 15.85598874092102s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.4100170135498047s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.3385319709777832s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.021997928619384766s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.557868957519531e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.4543533325195312e-05s
INFO | --- Analysis for linked-drugs took 8.204986810684204s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 9.083747863769531e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.3358638286590576s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.632110595703125e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 5.245208740234375e-06s
INFO | --- Analysis for linked-edgar took 4.947672605514526s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 5.340576171875e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.3117542266845703s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.560585021972656e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 8.106231689453125e-06s
INFO | --- Analysis for linked-eurostat took 4.0019354820251465s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.9591064453125e-05s
Availability | VoID file availability check for linked hypernyms took 0.0003323554992675781s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.34256505966186523s
Reputation | Calculation of the PageRank for linked hypernyms took 0.0209503173828125s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.462501525878906e-05s
Believability | Calculation of trust value for linked hypernyms took 7.3909759521484375e-06s
INFO | --- Analysis for linked-hypernyms took 3.8923001289367676s
Availability | SPARQL endpoint availability check for Linked Life Data took 242.08613872528076s
Availability | VoID file availability check for Linked Life Data took 0.0008463859558105469s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.5055527687072754s
Reputation | Calculation of the PageRank for Linked Life Data took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.8160552978515625e-05s
Believability | Calculation of trust value for Linked Life Data took 1.4066696166992188e-05s
INFO | --- Analysis for linked-life-data took 718.4172377586365s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.32798051834106445s
Availability | VoID file availability check for Linked Logainm took 0.0005383491516113281s
Extra | Recovery of all triples for Linked Logainm took 1.8690013885498047s
Performance | Total latancy measurement for Linked Logainm took 0.621617317199707s
Amount of data | Number of triples check for Linked Logainm took 0.182891845703125s
Interoperability | New terms check for Linked Logainm took 1.4579639434814453s
Versatility | Languages check for Linked Logainm took 1.4251747131347656s
Interpretability | Number of blank nodes check for Linked Logainm took 0.153181791305542s
Security | Check HTTPS for Linked Logainm took 0.29073333740234375s
Interpretability | RDF structures check for Linked Logainm took 0.2503812313079834s
Versatility | Serialization formats check for Linked Logainm took 0.16334772109985352s
Availability | RDF dump link check for Linked Logainm took 0.12201452255249023s
License | MR license check for Linked Logainm took 0.1342332363128662s
License | HR license check for Linked Logainm took 0.12702178955078125s
Amount of data | Number of property check for Linked Logainm took 0.16756701469421387s
Understandability | Number of label check for Linked Logainm took 0.20513272285461426s
Understandability | URI regex check for Linked Logainm took 0.2671010494232178s
Understandability | Vocabs check for Linked Logainm took 0.12323665618896484s
Verifiability | Authors check for Linked Logainm took 0.1256554126739502s
Verifiability | Publishers check for Linked Logainm took 0.23012661933898926s
Performance | Throughput check for Linked Logainm took 10.730025291442871s
Amount of data | Check the number of entities for Linked Logainm took 6.890296936035156e-05s
Verifiability | Contribs. check for Linked Logainm took 0.12427687644958496s
Interlinking | sameAs chians check for Linked Logainm took 0.15600943565368652s
Interlinking | skos check for Linked Logainm took 0.16463303565979004s
Interlinking | skos check for Linked Logainm took 0.12041020393371582s
Timeliness | dataset update frequency check for Linked Logainm took 0.12867283821105957s
Currency | Creation date check for Linked Logainm took 0.2794029712677002s
Currency | Modification date check for Linked Logainm took 0.2763700485229492s
Rep.Conc. | URIs length for Linked Logainm took 0.9324264526367188s
Interoperability | New vocabularies check for Linked Logainm took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.19473862648010254s
Accuracy | Check Functional Property for Linked Logainm took 0.22411513328552246s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.19028377532958984s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5634562969207764s
Accuracy | Check White space in annotation for Linked Logainm took 0.02437281608581543s
Accuracy | Check Datatype consistency for Linked Logainm took 0.028826475143432617s
Consistency | Disjoint class check for Linked Logainm took 0.19114136695861816s
Consistency | Check Misplaced properties for Linked Logainm took 0.3592069149017334s
Consistency | Misplaced classes for Linked Logainm took 0.30300045013427734s
Consistency | Check Ontology hijacking for Linked Logainm took 1.7709662914276123s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.233647108078003s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.444117546081543s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.0330052375793457s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.21641087532043457s
Security | Sign check for Linked Logainm took 0.13649296760559082s
Availability | Check URIs Dereferenciability for Linked Logainm took 1074.3551137447357s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.47251272201538086s
Reputation | Calculation of the PageRank for Linked Logainm took 0.021469831466674805s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.296966552734375e-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 1.3113021850585938e-05s
INFO | --- Analysis for linked-logainm took 1133.123459815979s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.363059997558594e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.31447434425354004s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.8650970458984375e-05s
Believability | Calculation of trust value for Linked NUTS took 5.0067901611328125e-06s
INFO | --- Analysis for linked-nuts took 2.944791078567505s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.5104241371154785s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.3142051696777344s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.790855407714844e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-camera took 4.585396766662598s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.45876932144165s
Availability | VoID file availability check for Linked Open Commerce took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.34035825729370117s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.147125244140625e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.2874603271484375e-05s
INFO | --- Analysis for linked-open-commerce took 15.502896547317505s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.1778972148895264s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.3375358581542969s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02180337905883789s
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.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010013580322265625s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.3113021850585938e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 4.16972279548645s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.506111145019531e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.3378913402557373s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.96453857421875e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.3828277587890625e-05s
INFO | --- Analysis for linked-open-numbers took 3.2260684967041016s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.31158876419067383s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.147125244140625e-05s
Believability | Calculation of trust value for Linked Open Piracy took 9.298324584960938e-06s
INFO | --- Analysis for linked-open-piracy took 8.126802921295166s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 2.018420457839966s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0006263256072998047s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 65.11068296432495s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 1.4124155044555664s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 1.7024693489074707s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 2.5128111839294434s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 12.898666620254517s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.3968124389648438s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 0.38931703567504883s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 0.22736501693725586s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 21.958244562149048s
License | MR license check for Linked Open Vocabularies (LOV) took 0.22024750709533691s
License | HR license check for Linked Open Vocabularies (LOV) took 45.76157569885254s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 0.3445703983306885s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 0.9806249141693115s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 0.4067385196685791s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 0.3479599952697754s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 0.45411205291748047s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 0.22788548469543457s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 11.181432962417603s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.0614144802093506s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 0.23392844200134277s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 0.22864961624145508s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.228712797164917s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.2324199676513672s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 0.21237730979919434s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 1.35245680809021s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 0.22455596923828125s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 24.743178606033325s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 18.00005555152893s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.27199363708496094s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.22851252555847168s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.20085883140563965s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 6.37252402305603s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6869194507598877s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.673810720443726s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.42841553688049316s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 6.6375908851623535s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.21742987632751465s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 5.662276983261108s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.3705077171325684s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.947495937347412s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 1.9658384323120117s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.61257004737854s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 6124.37332201004s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.7399160861968994s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.021193504333496094s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 3.6716461181640625e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 5.841255187988281e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 17.839006662368774s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 2.8133392333984375e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 7193.904450178146s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 9.322166442871094e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.3149259090423584s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02289128303527832s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.910064697265625e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 8.106231689453125e-06s
INFO | --- Analysis for linked-periodicals took 3.0769355297088623s
Availability | SPARQL endpoint availability check for Linked Index took 9.012222290039062e-05s
Availability | VoID file availability check for Linked Index took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Linked Index took 0.33490467071533203s
Reputation | Calculation of the PageRank for Linked Index took 0.021102190017700195s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.416175842285156e-05s
Believability | Calculation of trust value for Linked Index took 1.0967254638671875e-05s
INFO | --- Analysis for linked-stockindex took 3.503913164138794s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.48941445350647s
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.3405416011810303s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 4.57763671875e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.049041748046875e-05s
INFO | --- Analysis for linked-structured-product-labels took 20.965526819229126s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.3452925682067871s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.3375859260559082s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.021030902862548828s
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.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.5497207641601562e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 3.386279344558716s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.31553626060486s
Availability | VoID file availability check for Linked TCGA took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.3412210941314697s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.535385131835938e-05s
Believability | Calculation of trust value for Linked TCGA took 9.775161743164062e-06s
INFO | --- Analysis for linked-tcga took 63.38850378990173s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.12360072135925293s
Availability | VoID file availability check for Linked User Feedback took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.30643701553344727s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.021159648895263672s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 4.291534423828125e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.1682510375976562e-05s
INFO | --- Analysis for linked-user-feedback took 3.0564401149749756s
Availability | SPARQL endpoint availability check for USPTO Patent data took 8.916854858398438e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0007472038269042969s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.33257365226745605s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.368492126464844e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.0251998901367188e-05s
INFO | --- Analysis for linked-uspto-patent-data took 54.151755571365356s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.2204275131225586s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.3213059902191162s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02155327796936035s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.3589859008789062e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 3.601008176803589s
Availability | SPARQL endpoint availability check for LinkedCT took 1.7897818088531494s
Availability | VoID file availability check for LinkedCT took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.34033751487731934s
Reputation | Calculation of the PageRank for LinkedCT took 0.02105093002319336s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.5367431640625e-05s
Believability | Calculation of trust value for LinkedCT took 7.62939453125e-06s
INFO | --- Analysis for linkedct took 6.092337608337402s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.17901134490966797s
Availability | VoID file availability check for LinkedGeoData took 0.0009019374847412109s
Extra | Recovery of all triples for LinkedGeoData took 7.389053106307983s
Performance | Total latancy measurement for LinkedGeoData took 0.7018277645111084s
Amount of data | Number of triples check for LinkedGeoData took 96.62826108932495s
Interoperability | New terms check for LinkedGeoData took 91.09016489982605s
Versatility | Languages check for LinkedGeoData took 181.69227528572083s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.24925947189331055s
Security | Check HTTPS for LinkedGeoData took 0.3289191722869873s
Interpretability | RDF structures check for LinkedGeoData took 0.7967884540557861s
Versatility | Serialization formats check for LinkedGeoData took 0.3665151596069336s
Availability | RDF dump link check for LinkedGeoData took 0.16188311576843262s
License | MR license check for LinkedGeoData took 0.5865552425384521s
License | HR license check for LinkedGeoData took 105.56177425384521s
Amount of data | Number of property check for LinkedGeoData took 0.5659852027893066s
Understandability | Number of label check for LinkedGeoData took 2.340214729309082s
Understandability | URI regex check for LinkedGeoData took 0.39031147956848145s
Understandability | Vocabs check for LinkedGeoData took 0.1805884838104248s
Verifiability | Authors check for LinkedGeoData took 0.16165423393249512s
Verifiability | Publishers check for LinkedGeoData took 0.13443470001220703s
Performance | Throughput check for LinkedGeoData took 10.765642404556274s
Amount of data | Check the number of entities for LinkedGeoData took 0.06611371040344238s
Verifiability | Contribs. check for LinkedGeoData took 2.0704596042633057s
Interlinking | sameAs chians check for LinkedGeoData took 0.36385464668273926s
Interlinking | skos check for LinkedGeoData took 0.42461442947387695s
Interlinking | skos check for LinkedGeoData took 0.13330388069152832s
Timeliness | dataset update frequency check for LinkedGeoData took 0.3773458003997803s
Currency | Creation date check for LinkedGeoData took 0.5067844390869141s
Currency | Modification date check for LinkedGeoData took 2.8485305309295654s
Rep.Conc. | URIs length for LinkedGeoData took 272.81015729904175s
Interoperability | New vocabularies check for LinkedGeoData took 14.32657241821289s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.15088653564453125s
Accuracy | Check Functional Property for LinkedGeoData took 0.21387743949890137s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.17089533805847168s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.770153522491455s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15559983253479004s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13797259330749512s
Consistency | Disjoint class check for LinkedGeoData took 0.21697473526000977s
Consistency | Check Misplaced properties for LinkedGeoData took 182.2234308719635s
Consistency | Misplaced classes for LinkedGeoData took 0.6321477890014648s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.4859988689422607s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.2947473526000977s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 183.2892246246338s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.1524653434753418s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.4556550979614258s
Security | Sign check for LinkedGeoData took 0.7841024398803711s
Availability | Check URIs Dereferenciability for LinkedGeoData took 14.87117075920105s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.5929288864135742s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021387815475463867s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00012969970703125s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 12.968790054321289s
Believability | Calculation of trust value for LinkedGeoData took 1.239776611328125e-05s
INFO | --- Analysis for linkedgeodata took 2432.7533507347107s
Availability | SPARQL endpoint availability check for LinkedLCCN took 12.938797950744629s
Availability | VoID file availability check for LinkedLCCN took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.3724677562713623s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.021109580993652344s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 7.081031799316406e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010991096496582031s
Believability | Calculation of trust value for LinkedLCCN took 1.2159347534179688e-05s
INFO | --- Analysis for linkedlccn took 33.394479751586914s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 9.274482727050781e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.311384916305542s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.021344900131225586s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.4332275390625e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.2874603271484375e-05s
INFO | --- Analysis for linkedmarkmail took 3.169184446334839s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.63147020339966s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.31132984161376953s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02250385284423828s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.0001392364501953125s
Believability | Calculation of trust value for Linked Movie DataBase took 1.4543533325195312e-05s
INFO | --- Analysis for linkedmdb took 133.93174600601196s
Availability | SPARQL endpoint availability check for LinkedSpending took 0.7185361385345459s
Availability | VoID file availability check for LinkedSpending took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.31550168991088867s
Reputation | Calculation of the PageRank for LinkedSpending took 0.021152496337890625s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedSpending took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 8.153915405273438e-05s
Believability | Calculation of trust value for LinkedSpending took 1.2636184692382812e-05s
INFO | --- Analysis for linkedspending took 4.859530687332153s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.08602547645568848s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.33743715286254883s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010919570922851562s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.33514404296875e-05s
INFO | --- Analysis for linklion took 3.15258526802063s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 319.2332909107208s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.34009313583374023s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.021636009216308594s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.817413330078125e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.3589859008789062e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 634.3168687820435s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.3023369312286377s
Availability | VoID file availability check for lobid-organisations took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.3125331401824951s
Reputation | Calculation of the PageRank for lobid-organisations took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0009105205535888672s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.0001049041748046875s
Believability | Calculation of trust value for lobid-organisations took 1.239776611328125e-05s
INFO | --- Analysis for lobid-organisations took 6.303548812866211s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.7943675518035889s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.3101842403411865s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.022396087646484375s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010204315185546875s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.049041748046875e-05s
INFO | --- Analysis for lobid-resources took 8.095900535583496s
Availability | SPARQL endpoint availability check for Linked Open Colors took 0.00013256072998046875s
Availability | VoID file availability check for Linked Open Colors took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.3149263858795166s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.0229032039642334s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.605552673339844e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.239776611328125e-05s
INFO | --- Analysis for loc took 8.300991535186768s
Availability | SPARQL endpoint availability check for Location Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Location Ontology took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.3395843505859375s
Reputation | Calculation of the PageRank for Location Ontology took 0.02189350128173828s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for Location Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for Location_Ontology took 6.1197264194488525s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 9.250640869140625e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.33087706565856934s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.02100372314453125s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.2874603271484375e-05s
INFO | --- Analysis for locv took 35.48258018493652s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.8234655857086182s
Availability | VoID file availability check for LOD-a-lot took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.3355109691619873s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.956390380859375e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.2636184692382812e-05s
INFO | --- Analysis for lod-a-lot took 14.626633167266846s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.458427429199219e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.3471837043762207s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.463859558105469e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 6.198883056640625e-06s
INFO | --- Analysis for lod2-project-wiki took 3.903533697128296s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.7141973972320557s
Availability | VoID file availability check for LODAC BDLS took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.3402726650238037s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0008175373077392578s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 8.606910705566406e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.3828277587890625e-05s
INFO | --- Analysis for lodac-bdls took 14.298785924911499s
Availability | SPARQL endpoint availability check for lofd took 0.13119077682495117s
Availability | VoID file availability check for lofd took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for lofd took 0.34039807319641113s
Reputation | Calculation of the PageRank for lofd took 0.022930622100830078s
Interlinking | Calculation of Degree of Connection for lofd took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for lofd took 3.147125244140625e-05s
Believability | Calculation of trust value for lofd took 1.2159347534179688e-05s
INFO | --- Analysis for lofd took 3.1876742839813232s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 270.9939315319061s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.3397939205169678s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021451473236083984s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.7697296142578125e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 3.1948089599609375e-05s
INFO | --- Analysis for loius took 585.2187325954437s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 1.536588430404663s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.3391914367675781s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.0210418701171875s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.4836273193359375e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 8.106231689453125e-06s
INFO | --- Analysis for london-gazette took 5.998511791229248s
Availability | SPARQL endpoint availability check for Weather Stations took 4.76837158203125e-05s
Availability | VoID file availability check for Weather Stations took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.3102846145629883s
Reputation | Calculation of the PageRank for Weather Stations took 0.022495269775390625s
Interlinking | Calculation of Degree of Connection for Weather Stations took 3.218650817871094e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.002095460891723633s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 0.0001964569091796875s
Believability | Calculation of trust value for Weather Stations took 1.3828277587890625e-05s
INFO | --- Analysis for los_metar took 9.044060230255127s
Availability | SPARQL endpoint availability check for Lotico took 0.4135305881500244s
Availability | VoID file availability check for Lotico took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Lotico took 0.3402895927429199s
Reputation | Calculation of the PageRank for Lotico took 0.0213775634765625s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.153915405273438e-05s
Believability | Calculation of trust value for Lotico took 1.049041748046875e-05s
INFO | --- Analysis for lotico took 5.190736293792725s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.3676462173461914s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0006330013275146484s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.3624873161315918s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 1.557375431060791s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.23229575157165527s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.6412420272827148s
Versatility | Languages check for Lower Layer Super Output Areas took 0.4090604782104492s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.235016345977783s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.1842482089996338s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.23001623153686523s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.16819310188293457s
Availability | RDF dump link check for Lower Layer Super Output Areas took 54.030431270599365s
License | MR license check for Lower Layer Super Output Areas took 0.23093581199645996s
License | HR license check for Lower Layer Super Output Areas took 30.261244535446167s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.233443021774292s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.16149616241455078s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.32190561294555664s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.1614518165588379s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.22673964500427246s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.1596360206604004s
Performance | Throughput check for Lower Layer Super Output Areas took 11.521337270736694s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 7.796287536621094e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.1606919765472412s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.15723395347595215s
Interlinking | skos check for Lower Layer Super Output Areas took 0.2335679531097412s
Interlinking | skos check for Lower Layer Super Output Areas took 0.6173787117004395s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.16882634162902832s
Currency | Creation date check for Lower Layer Super Output Areas took 0.42120885848999023s
Currency | Modification date check for Lower Layer Super Output Areas took 0.16797947883605957s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.626709222793579s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.16897201538085938s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.2249603271484375s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.22851276397705078s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.22554612159729004s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.6798629760742188s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.0629827976226807s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.5577001571655273s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.0001747608184814453s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.46930480003356934s
Security | Sign check for Lower Layer Super Output Areas took 0.22937250137329102s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.3505523204803467s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.6689300537109375e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.0251998901367188e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 277.720906496048s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.652738094329834s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0004913806915283203s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 105.4038736820221s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0523803234100342s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.178212881088257s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.304248332977295s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.22812938690186s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.4638047218322754s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.39424777030944824s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.039226770401001s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.37966322898864746s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9433529376983643s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.18090415000916s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24847745895385742s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.7052552700042725s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.107945442199707s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.47986721992492676s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.237152099609375s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.26937198638916016s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.447208642959595s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.224082946777344e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2146897315979004s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22465109825134277s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5412287712097168s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.48454928398132324s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.87960147857666s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.581186056137085s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.27434778213500977s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 156.54312467575073s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22031164169311523s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5378978252410889s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5029191970825195s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 38.436628580093384s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.765770435333252s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.1665799617767334s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21839570999145508s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 85.65182590484619s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.211002111434937s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 31.52047610282898s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.33282470703125s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.36742424964905s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7926414012908936s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0256164073944092s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.6290442943572998s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.04502272605896s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5974299907684326s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.02145695686340332s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.797645568847656e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for LPIS_(Poland) took 2294.1414074897766s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2163374423980713s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0004794597625732422s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 107.96760845184326s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0542426109313965s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.970443487167358s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.168702602386475s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.1795060634613s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9044125080108643s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.23231291770935059s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.300137519836426s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21261167526245117s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.23139548301696777s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.21781039237976s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2119448184967041s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3000333309173584s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.42052125930786133s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21820735931396484s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20937895774841309s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.26561784744262695s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.554645299911499s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.00011038780212402344s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21082115173339844s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21092820167541504s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.49380064010620117s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4396798610687256s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.829974412918091s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5322988033294678s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2565286159515381s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 154.60657238960266s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2086477279663086s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20754146575927734s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21280169486999512s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.52668023109436s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.691296339035034s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.760230779647827s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21017932891845703s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.30301856994629s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.414853811264038s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.0864462852478s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.322272777557373s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.65915393829346s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.8983542919158936s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5832934379577637s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22712945938110352s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.293579578399658s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8186197280883789s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021269798278808594s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.0531158447265625e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2286.939593076706s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 9.393692016601562e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.3087949752807617s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020852088928222656s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.647804260253906e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.049041748046875e-05s
INFO | --- Analysis for lremap-auth took 3.632763147354126s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 0.00020456314086914062s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.31111621856689453s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.021278858184814453s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.123283386230469e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 9.5367431640625e-06s
INFO | --- Analysis for lremap-conf took 3.176097869873047s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 9.012222290039062e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.33093810081481934s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020868778228759766s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.266334533691406e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.0013580322265625e-05s
INFO | --- Analysis for lremap-ri took 3.2358763217926025s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00012350082397460938s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.30994153022766113s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.021178483963012695s
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.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.2901763916015625e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.0013580322265625e-05s
INFO | --- Analysis for lremap-sub took 3.214609384536743s
Availability | SPARQL endpoint availability check for LSQ took 4.482269287109375e-05s
Availability | VoID file availability check for LSQ took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for LSQ took 0.3385012149810791s
Reputation | Calculation of the PageRank for LSQ took 0.02118968963623047s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.266334533691406e-05s
Believability | Calculation of trust value for LSQ took 1.1920928955078125e-05s
INFO | --- Analysis for lsq took 4.037081956863403s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.7337439060211182s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.3393242359161377s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02253246307373047s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for LucaniPharsalia took 4.891072750091553s
Availability | SPARQL endpoint availability check for Linked rules took 8.869171142578125e-05s
Availability | VoID file availability check for Linked rules took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Linked rules took 0.33783626556396484s
Reputation | Calculation of the PageRank for Linked rules took 0.021720170974731445s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.361701965332031e-05s
Believability | Calculation of trust value for Linked rules took 9.775161743164062e-06s
INFO | --- Analysis for Luminaires_senlis took 2.9191977977752686s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.117908716201782s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.30802345275878906s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.021054506301879883s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.218650817871094e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.049041748046875e-05s
INFO | --- Analysis for makg took 70.33787870407104s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 0.0001418590545654297s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.3108329772949219s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.62396240234375e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.1920928955078125e-05s
INFO | --- Analysis for manchester-university-reading-lists took 6.804527997970581s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 9.083747863769531e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.34806227684020996s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02243971824645996s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0517578125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 9.298324584960938e-06s
INFO | --- Analysis for manish took 2.9195923805236816s
Availability | SPARQL endpoint availability check for MARC Codes List took 6.532669067382812e-05s
Availability | VoID file availability check for MARC Codes List took 0.0013401508331298828s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.3409426212310791s
Reputation | Calculation of the PageRank for MARC Codes List took 0.021097183227539062s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00013446807861328125s
Believability | Calculation of trust value for MARC Codes List took 1.049041748046875e-05s
INFO | --- Analysis for marc-codes took 13.553339719772339s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.012222290039062e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.36130309104919434s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.022499561309814453s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.124641418457031e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1205673217773438e-05s
INFO | --- Analysis for masc took 13.179635763168335s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 8.702278137207031e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.33693671226501465s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.022049665451049805s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.9577484130859375e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.0728836059570312e-05s
INFO | --- Analysis for masc-bn-nif took 3.0413665771484375s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.2150499820709229s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.34336042404174805s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.075599670410156e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 8.821487426757812e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.384156703948975s
Availability | SPARQL endpoint availability check for medline took 8.559226989746094e-05s
Availability | VoID file availability check for medline took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for medline took 0.332935094833374s
Reputation | Calculation of the PageRank for medline took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for medline took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for medline took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for medline took 3.838539123535156e-05s
Believability | Calculation of trust value for medline took 1.2636184692382812e-05s
INFO | --- Analysis for medline took 8.489885091781616s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 2.0078253746032715s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.30939674377441406s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.033348083496094e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.0013580322265625e-05s
INFO | --- Analysis for meducator took 13.643867492675781s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.482269287109375e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.31122326850891113s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.02167224884033203s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.62939453125e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.1682510375976562e-05s
INFO | --- Analysis for metashare took 3.0529797077178955s
Availability | SPARQL endpoint availability check for MExiCo took 9.226799011230469e-05s
Availability | VoID file availability check for MExiCo took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for MExiCo took 0.33825206756591797s
Reputation | Calculation of the PageRank for MExiCo took 0.020955324172973633s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.555152893066406e-05s
Believability | Calculation of trust value for MExiCo took 1.1205673217773438e-05s
INFO | --- Analysis for mexico took 23.094080209732056s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.1560237407684326s
Availability | VoID file availability check for Coronavirus dataset took 0.0005035400390625s
Extra | Recovery of all triples for Coronavirus dataset took 6.144770622253418s
Performance | Total latancy measurement for Coronavirus dataset took 2.527456760406494s
Amount of data | Number of triples check for Coronavirus dataset took 1.1887166500091553s
Interoperability | New terms check for Coronavirus dataset took 2.5611698627471924s
Versatility | Languages check for Coronavirus dataset took 60.52788019180298s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.598693609237671s
Interpretability | RDF structures check for Coronavirus dataset took 0.5459318161010742s
Versatility | Serialization formats check for Coronavirus dataset took 0.5542519092559814s
Availability | RDF dump link check for Coronavirus dataset took 0.5030941963195801s
License | MR license check for Coronavirus dataset took 0.5717005729675293s
License | HR license check for Coronavirus dataset took 41.30204939842224s
Amount of data | Number of property check for Coronavirus dataset took 0.5421216487884521s
Understandability | Number of label check for Coronavirus dataset took 1.4915246963500977s
Understandability | URI regex check for Coronavirus dataset took 1.008049488067627s
Understandability | Vocabs check for Coronavirus dataset took 0.508028507232666s
Verifiability | Authors check for Coronavirus dataset took 0.5854706764221191s
Verifiability | Publishers check for Coronavirus dataset took 0.50681471824646s
Performance | Throughput check for Coronavirus dataset took 14.479543924331665s
Amount of data | Check the number of entities for Coronavirus dataset took 7.390975952148438e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5079302787780762s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5429234504699707s
Interlinking | skos check for Coronavirus dataset took 0.5608556270599365s
Interlinking | skos check for Coronavirus dataset took 0.5009400844573975s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5104849338531494s
Currency | Creation date check for Coronavirus dataset took 1.0441327095031738s
Currency | Modification date check for Coronavirus dataset took 1.0397143363952637s
Rep.Conc. | URIs length for Coronavirus dataset took 8.444530248641968s
Interoperability | New vocabularies check for Coronavirus dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5355489253997803s
Accuracy | Check Functional Property for Coronavirus dataset took 0.6905515193939209s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.6819686889648438s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.1320953369140625s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022797107696533203s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.029059171676635742s
Consistency | Disjoint class check for Coronavirus dataset took 0.9191186428070068s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.679642915725708s
Consistency | Misplaced classes for Coronavirus dataset took 0.6299102306365967s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.389785051345825s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.300377607345581s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 7.003290891647339s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03296971321105957s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5381042957305908s
Security | Sign check for Coronavirus dataset took 0.5140852928161621s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3218.6413102149963s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.886171817779541s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021435260772705078s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 2.956390380859375e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 7.510185241699219e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.2636184692382812e-05s
INFO | --- Analysis for micro-coronavirus took 3460.4258828163147s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.5299530029296875e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.3331139087677002s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020181894302368164s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010514259338378906s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 5.7220458984375e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 6.135030269622803s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.893013000488281e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.3367772102355957s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011277198791503906s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0967254638671875e-05s
INFO | --- Analysis for mismuseos-gnoss took 5.633443355560303s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.1214444637298584s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.310685396194458s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020833253860473633s
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.000701904296875s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.696846008300781e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.3909759521484375e-06s
INFO | --- Analysis for mlsa took 3.686119556427002s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.482269287109375e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.31186819076538086s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.1920928955078125e-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.075599670410156e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.2159347534179688e-05s
INFO | --- Analysis for model took 35.922932147979736s
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.553794860839844e-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.0006861686706542969s
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.3127739429473877s
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.02053070068359375s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 3.123283386230469e-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 1.1444091796875e-05s
INFO | --- Analysis for model1 took 21.198015689849854s
Availability | SPARQL endpoint availability check for MORElab took 1.1463871002197266s
Availability | VoID file availability check for MORElab took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for MORElab took 0.333172082901001s
Reputation | Calculation of the PageRank for MORElab took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for MORElab took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MORElab took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.869171142578125e-05s
Believability | Calculation of trust value for MORElab took 6.4373016357421875e-06s
INFO | --- Analysis for morelab took 5.8690266609191895s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.253568172454834s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.31236791610717773s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.630752563476562e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 5.4836273193359375e-06s
INFO | --- Analysis for msc took 17.525185346603394s
Availability | SPARQL endpoint availability check for Multext-East took 4.4345855712890625e-05s
Availability | VoID file availability check for Multext-East took 0.00021719932556152344s
Completeness | Calculation of interlinking completeness for Multext-East took 0.30803799629211426s
Reputation | Calculation of the PageRank for Multext-East took 0.020833730697631836s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.62396240234375e-05s
Believability | Calculation of trust value for Multext-East took 5.245208740234375e-06s
INFO | --- Analysis for multext-east took 2.8940658569335938s
Availability | SPARQL endpoint availability check for Multimedia Lab took 7.581710815429688e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.3326897621154785s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.021610260009765625s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.409385681152344e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.0728836059570312e-05s
INFO | --- Analysis for multimedia-lab took 2.9382383823394775s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.6773004531860352s
Availability | VoID file availability check for Muninn World War I took 0.0003185272216796875s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.3127632141113281s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.368492126464844e-05s
Believability | Calculation of trust value for Muninn World War I took 6.198883056640625e-06s
INFO | --- Analysis for muninn-world-war-i took 11.502737760543823s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 5.7697296142578125e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.35805845260620117s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.02095961570739746s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.000118255615234375s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.2874603271484375e-05s
INFO | --- Analysis for museosespania-gnoss took 77.9396333694458s
Availability | SPARQL endpoint availability check for Italian Museums took 1.5506632328033447s
Availability | VoID file availability check for Italian Museums took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.31005334854125977s
Reputation | Calculation of the PageRank for Italian Museums took 0.021936655044555664s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.726119995117188e-05s
Believability | Calculation of trust value for Italian Museums took 1.33514404296875e-05s
INFO | --- Analysis for museums-in-italy took 4.627147912979126s
Availability | SPARQL endpoint availability check for Muziekweb took 0.8004913330078125s
Availability | VoID file availability check for Muziekweb took 0.0006203651428222656s
Extra | Recovery of all triples for Muziekweb took 1.7224693298339844s
Performance | Total latancy measurement for Muziekweb took 1.6507813930511475s
Amount of data | Number of triples check for Muziekweb took 0.42125368118286133s
Interoperability | New terms check for Muziekweb took 1.6817455291748047s
Versatility | Languages check for Muziekweb took 51.92153978347778s
Interpretability | Number of blank nodes check for Muziekweb took 0.3503732681274414s
Interpretability | RDF structures check for Muziekweb took 0.3826165199279785s
Versatility | Serialization formats check for Muziekweb took 0.36774539947509766s
Availability | RDF dump link check for Muziekweb took 0.3840146064758301s
License | MR license check for Muziekweb took 0.3448364734649658s
License | HR license check for Muziekweb took 11.118375778198242s
Amount of data | Number of property check for Muziekweb took 0.32207632064819336s
Understandability | Number of label check for Muziekweb took 0.4146113395690918s
Understandability | URI regex check for Muziekweb took 0.6813690662384033s
Understandability | Vocabs check for Muziekweb took 0.3334677219390869s
Verifiability | Authors check for Muziekweb took 0.34233689308166504s
Verifiability | Publishers check for Muziekweb took 0.34856247901916504s
Performance | Throughput check for Muziekweb took 11.390318393707275s
Amount of data | Check the number of entities for Muziekweb took 7.319450378417969e-05s
Verifiability | Contribs. check for Muziekweb took 0.3374190330505371s
Interlinking | sameAs chians check for Muziekweb took 0.36644721031188965s
Interlinking | skos check for Muziekweb took 0.3887941837310791s
Interlinking | skos check for Muziekweb took 0.32407712936401367s
Timeliness | dataset update frequency check for Muziekweb took 0.3401069641113281s
Currency | Creation date check for Muziekweb took 0.9256219863891602s
Currency | Modification date check for Muziekweb took 0.9123775959014893s
Rep.Conc. | URIs length for Muziekweb took 2.058138847351074s
Interoperability | New vocabularies check for Muziekweb took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.3546173572540283s
Accuracy | Check Empty annotation labels for Muziekweb took 0.8930027484893799s
Accuracy | Check White space in annotation for Muziekweb took 0.027731657028198242s
Accuracy | Check Datatype consistency for Muziekweb took 0.030065536499023438s
Consistency | Disjoint class check for Muziekweb took 0.630122184753418s
Consistency | Check Misplaced properties for Muziekweb took 1.1996896266937256s
Consistency | Check Ontology hijacking for Muziekweb took 2.12345290184021s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.2419002056121826s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.606083869934082s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03464055061340332s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3378877639770508s
Security | Sign check for Muziekweb took 0.3472788333892822s
Availability | Check URIs Dereferenciability for Muziekweb took 2167.383275270462s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5646841526031494s
Reputation | Calculation of the PageRank for Muziekweb took 0.020723342895507812s
Interlinking | Calculation of Degree of Connection for Muziekweb took 2.8133392333984375e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.723403930664062e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.1920928955078125e-06s
Believability | Calculation of trust value for Muziekweb took 1.33514404296875e-05s
INFO | --- Analysis for muziekweb took 2294.0266230106354s
Availability | SPARQL endpoint availability check for myExperiment took 0.5766811370849609s
Availability | VoID file availability check for myExperiment took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for myExperiment took 0.3113436698913574s
Reputation | Calculation of the PageRank for myExperiment took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010204315185546875s
Believability | Calculation of trust value for myExperiment took 1.1920928955078125e-05s
INFO | --- Analysis for my-experiment took 4.738978385925293s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.08627438545227051s
Availability | VoID file availability check for My Family Lineage took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.3358001708984375s
Reputation | Calculation of the PageRank for My Family Lineage took 0.021089553833007812s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.988380432128906e-05s
Believability | Calculation of trust value for My Family Lineage took 1.0967254638671875e-05s
INFO | --- Analysis for my-family-lineage took 4.377397537231445s
Availability | SPARQL endpoint availability check for My ontology test took 10.613629341125488s
Availability | VoID file availability check for My ontology test took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for My ontology test took 0.3094971179962158s
Reputation | Calculation of the PageRank for My ontology test took 0.020856857299804688s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.123283386230469e-05s
Believability | Calculation of trust value for My ontology test took 1.0967254638671875e-05s
INFO | --- Analysis for myontologytest took 13.72954773902893s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 8.988380432128906e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.31711411476135254s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.0224149227142334s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010013580322265625s
Believability | Calculation of trust value for myopenlink dataspaces took 1.3113021850585938e-05s
INFO | --- Analysis for myopenlink-dataspaces took 3.511068820953369s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 7.881084680557251s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.3103811740875244s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02115464210510254s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.985664367675781e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for n-lex-as-linked-data took 19.959602117538452s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.1714985370636s
Availability | VoID file availability check for NAICS 2007 took 0.0007710456848144531s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.31227612495422363s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02929973602294922s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.1961669921875e-05s
Believability | Calculation of trust value for NAICS 2007 took 8.821487426757812e-06s
INFO | --- Analysis for naics-2007 took 126.09835815429688s
Availability | SPARQL endpoint availability check for NAICS 2012 took 25.06588912010193s
Availability | VoID file availability check for NAICS 2012 took 0.0007624626159667969s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.3430044651031494s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.887580871582031e-05s
Believability | Calculation of trust value for NAICS 2012 took 8.344650268554688e-06s
INFO | --- Analysis for naics-2012 took 124.35699820518494s
Availability | SPARQL endpoint availability check for Usernames  took 4.291534423828125e-05s
Availability | VoID file availability check for Usernames  took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Usernames  took 0.34301114082336426s
Reputation | Calculation of the PageRank for Usernames  took 0.020708560943603516s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Usernames  took 2.9802322387695312e-05s
Believability | Calculation of trust value for Usernames  took 1.0728836059570312e-05s
INFO | --- Analysis for Names took 3.1289548873901367s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.4968059062957764s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0005795955657958984s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.5689177513122559s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.2821710109710693s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.097445249557495s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 14.01924467086792s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.9109337329864502s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.343874454498291s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.8779757022857666s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.390061616897583s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.41644954681396484s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.396956205368042s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.9002842903137207s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.43701386451721s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9535012245178223s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.213642120361328s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.8280746936798096s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.8432695865631104s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.440962553024292s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.39897942543029785s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 15.25357699394226s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.821487426757812e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.40909552574157715s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.5445692539215088s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.7416577339172363s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.1022748947143555s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3979625701904297s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.2598156929016113s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 1.3150010108947754s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.8269426822662354s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.4226346015930176s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.39618635177612305s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.4033944606781006s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.42078161239624023s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007319450378417969s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.001046895980834961s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.872999906539917s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.8476283550262451s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.40781641006469727s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.7328729629516602s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.3144874572753906s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.6672027111053467s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006747245788574219s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.390911340713501s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 5.790685653686523s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.34519410133361816s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.021553754806518555s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 7.009506225585938e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 6.198883056640625e-06s
INFO | --- Analysis for national-diet-library-authorities took 244.16939997673035s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.42615842819213867s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006375312805175781s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.520672082901001s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.9895877838134766s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.42139744758606s
Interoperability | New terms check for National Diet Library of Japan subject headings took 13.764071702957153s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.44124865531921387s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.286827802658081s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.374636173248291s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.43152427673339844s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.8590636253356934s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.39308786392211914s
License | MR license check for National Diet Library of Japan subject headings took 0.8912174701690674s
License | HR license check for National Diet Library of Japan subject headings took 91.89034295082092s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.9832048416137695s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.213455438613892s
Understandability | URI regex check for National Diet Library of Japan subject headings took 1.3434631824493408s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.8877766132354736s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.4201784133911133s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.4128999710083008s
Performance | Throughput check for National Diet Library of Japan subject headings took 12.333576202392578s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.606910705566406e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.88089919090271s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.4868741035461426s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.762239933013916s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.114013671875s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.4075312614440918s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.2460260391235352s
Currency | Modification date check for National Diet Library of Japan subject headings took 1.3405015468597412s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.8172895908355713s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.8879959583282471s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.4103693962097168s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.40596461296081543s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.42151832580566406s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007307529449462891s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010290145874023438s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.4065580368041992s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.8396823406219482s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.41179895401000977s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 2.232062816619873s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.3125343322753906s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.713045358657837s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.000682830810546875s
Security | Sign check for National Diet Library of Japan subject headings took 0.42267298698425293s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 5.728677272796631s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.410675048828125s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.021056652069091797s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 5.0067901611328125e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 238.28981804847717s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.3125202655792236s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.34074950218200684s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.021149158477783203s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.696846008300781e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.049041748046875e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 6.698651075363159s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.369850158691406e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.3097653388977051s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.021218061447143555s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.2479248046875e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.049041748046875e-05s
INFO | --- Analysis for Naturopathy took 3.5995185375213623s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.458174228668213s
Availability | VoID file availability check for COVID-19 Data took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.337568998336792s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.021188974380493164s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.361701965332031e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.049041748046875e-05s
INFO | --- Analysis for NCMI-COVID-19 took 7.8832526206970215s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.43894624710083s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.33924436569213867s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.021103382110595703s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.239776611328125e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 9.775161743164062e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.89149022102356s
Availability | SPARQL endpoint availability check for Near took 8.916854858398438e-05s
Availability | VoID file availability check for Near took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Near took 0.34441304206848145s
Reputation | Calculation of the PageRank for Near took 0.021090030670166016s
Interlinking | Calculation of Degree of Connection for Near took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Near took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Near took 9.846687316894531e-05s
Believability | Calculation of trust value for Near took 1.1682510375976562e-05s
INFO | --- Analysis for near took 9.203514814376831s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 9.417533874511719e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.3152627944946289s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.02217698097229004s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.552436828613281e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.0013580322265625e-05s
INFO | --- Analysis for neurolex-wiki took 2.859976291656494s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 0.00011730194091796875s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.3089933395385742s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.02099156379699707s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.673004150390625e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 9.775161743164062e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 4.722679376602173s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 8.749961853027344e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.33896732330322266s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.02106928825378418s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 7.152557373046875e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 9.775161743164062e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.782682418823242s
Availability | SPARQL endpoint availability check for neXtProt took 1.9629621505737305s
Availability | VoID file availability check for neXtProt took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for neXtProt took 0.3365943431854248s
Reputation | Calculation of the PageRank for neXtProt took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for neXtProt took 5.5789947509765625e-05s
Believability | Calculation of trust value for neXtProt took 1.3113021850585938e-05s
INFO | --- Analysis for nextprot took 5.654043912887573s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010633468627929688s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0003631114959716797s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.3083212375640869s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010228157043457031s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for nextweb-gnoss took 8.911617279052734s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.38690185546875e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.340848445892334s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.021368026733398438s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.058547973632812e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 9.298324584960938e-06s
INFO | --- Analysis for nhs-jargon took 3.457580327987671s
Availability | SPARQL endpoint availability check for NIT Patna took 9.179115295410156e-05s
Availability | VoID file availability check for NIT Patna took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.3132305145263672s
Reputation | Calculation of the PageRank for NIT Patna took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.937980651855469e-05s
Believability | Calculation of trust value for NIT Patna took 1.0728836059570312e-05s
INFO | --- Analysis for NITP took 3.9673449993133545s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 9.655952453613281e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0003571510314941406s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.3059825897216797s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.021744728088378906s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.647804260253906e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for nlr-dataset-mod took 4.534697771072388s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.7605037689208984s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.3425869941711426s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.3589859008789062e-05s
INFO | --- Analysis for NLW took 5.008104562759399s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.7213032245635986s
Availability | VoID file availability check for Nobel Prizes took 0.0012264251708984375s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.3162214756011963s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.870529174804688e-05s
Believability | Calculation of trust value for Nobel Prizes took 1.2874603271484375e-05s
INFO | --- Analysis for nobelprizes took 10.707034587860107s
Availability | SPARQL endpoint availability check for NoiPA took 0.4384646415710449s
Availability | VoID file availability check for NoiPA took 0.0002675056457519531s
Extra | Recovery of all triples for NoiPA took 1.1648664474487305s
Performance | Total latancy measurement for NoiPA took 0.6885271072387695s
Amount of data | Number of triples check for NoiPA took 1.2833054065704346s
Interoperability | New terms check for NoiPA took 2.758063554763794s
Versatility | Languages check for NoiPA took 60.20533633232117s
Interpretability | Number of blank nodes check for NoiPA took 0.24708008766174316s
Interpretability | RDF structures check for NoiPA took 0.20316386222839355s
Versatility | Serialization formats check for NoiPA took 0.15861964225769043s
Availability | RDF dump link check for NoiPA took 0.19998431205749512s
License | MR license check for NoiPA took 0.19678664207458496s
License | HR license check for NoiPA took 60.19730067253113s
Amount of data | Number of property check for NoiPA took 0.24201273918151855s
Understandability | Number of label check for NoiPA took 0.7068033218383789s
Understandability | URI regex check for NoiPA took 0.31435132026672363s
Understandability | Vocabs check for NoiPA took 0.13022398948669434s
Verifiability | Authors check for NoiPA took 0.12642645835876465s
Verifiability | Publishers check for NoiPA took 0.13777613639831543s
Performance | Throughput check for NoiPA took 10.585503816604614s
Amount of data | Check the number of entities for NoiPA took 7.009506225585938e-05s
Verifiability | Contribs. check for NoiPA took 0.13642024993896484s
Interlinking | sameAs chians check for NoiPA took 0.14058518409729004s
Interlinking | skos check for NoiPA took 0.18788576126098633s
Interlinking | skos check for NoiPA took 0.13038015365600586s
Timeliness | dataset update frequency check for NoiPA took 0.18834185600280762s
Currency | Creation date check for NoiPA took 0.3618447780609131s
Currency | Modification date check for NoiPA took 0.16127419471740723s
Rep.Conc. | URIs length for NoiPA took 18.13344669342041s
Interoperability | New vocabularies check for NoiPA took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.19230365753173828s
Accuracy | Check Functional Property for NoiPA took 0.14159059524536133s
Accuracy | Check Inverse Functional Property for NoiPA took 0.13350772857666016s
Accuracy | Check Empty annotation labels for NoiPA took 0.40288257598876953s
Accuracy | Check White space in annotation for NoiPA took 0.02608489990234375s
Accuracy | Check Datatype consistency for NoiPA took 0.028464317321777344s
Consistency | Disjoint class check for NoiPA took 0.1253218650817871s
Consistency | Check Misplaced properties for NoiPA took 16.157469511032104s
Consistency | Misplaced classes for NoiPA took 0.3123335838317871s
Consistency | Check Ontology hijacking for NoiPA took 1.6440794467926025s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.2531845569610596s
Consistency | Check Invalid usage of undefined properties for NoiPA took 17.205864667892456s
Conciseness | Check Extensional conciseness for NoiPA took 0.034859418869018555s
Conciseness | Check Intensional conciseness for NoiPA took 0.1844158172607422s
Security | Sign check for NoiPA took 0.13066482543945312s
Availability | Check URIs Dereferenciability for NoiPA took 14.501039505004883s
Completeness | Calculation of interlinking completeness for NoiPA took 2.130281448364258s
Reputation | Calculation of the PageRank for NoiPA took 0.021031856536865234s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0009677410125732422s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.6689300537109375e-06s
Believability | Calculation of trust value for NoiPA took 1.3113021850585938e-05s
INFO | --- Analysis for NoiPA took 502.4447412490845s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.2180159091949463s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.337615966796875s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02251148223876953s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0010101795196533203s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 0.00010991096496582031s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.33514404296875e-05s
INFO | --- Analysis for nom took 9.580161333084106s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 26.078003406524658s
Availability | VoID file availability check for Nomenclator Asturias took 0.0007987022399902344s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.37233853340148926s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.702278137207031e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 9.059906005859375e-06s
INFO | --- Analysis for nomenclator-asturias took 143.60595226287842s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.5343670845031738s
Availability | VoID file availability check for Nomisma.org  took 0.0005483627319335938s
Extra | Recovery of all triples for Nomisma.org  took 526.3939955234528s
Performance | Total latancy measurement for Nomisma.org  took 1.720928430557251s
Amount of data | Number of triples check for Nomisma.org  took 52.76653981208801s
Interoperability | New terms check for Nomisma.org  took 10.09570574760437s
Versatility | Languages check for Nomisma.org  took 132.48534226417542s
Interpretability | Number of blank nodes check for Nomisma.org  took 56.2769033908844s
Security | Check HTTPS for Nomisma.org  took 0.7694871425628662s
Interpretability | RDF structures check for Nomisma.org  took 0.36638474464416504s
Versatility | Serialization formats check for Nomisma.org  took 0.3649899959564209s
Availability | RDF dump link check for Nomisma.org  took 1131.7692639827728s
License | MR license check for Nomisma.org  took 0.45636844635009766s
License | HR license check for Nomisma.org  took 59.92083191871643s
Amount of data | Number of property check for Nomisma.org  took 0.3718881607055664s
Understandability | Number of label check for Nomisma.org  took 6.767002582550049s
Understandability | URI regex check for Nomisma.org  took 0.6426758766174316s
Understandability | Vocabs check for Nomisma.org  took 0.30657482147216797s
Verifiability | Authors check for Nomisma.org  took 0.32500147819519043s
Verifiability | Publishers check for Nomisma.org  took 0.3478078842163086s
Performance | Throughput check for Nomisma.org  took 12.087729215621948s
Amount of data | Check the number of entities for Nomisma.org  took 60.56532096862793s
Verifiability | Contribs. check for Nomisma.org  took 0.3815946578979492s
Interlinking | sameAs chians check for Nomisma.org  took 0.34871602058410645s
Interlinking | skos check for Nomisma.org  took 1.2274959087371826s
Interlinking | skos check for Nomisma.org  took 1.020683765411377s
Timeliness | dataset update frequency check for Nomisma.org  took 0.2907085418701172s
Currency | Creation date check for Nomisma.org  took 0.6781618595123291s
Currency | Modification date check for Nomisma.org  took 0.6554069519042969s
Rep.Conc. | URIs length for Nomisma.org  took 211.3378415107727s
Interoperability | New vocabularies check for Nomisma.org  took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.3414003849029541s
Accuracy | Check Functional Property for Nomisma.org  took 0.36500024795532227s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3332977294921875s
Accuracy | Check Empty annotation labels for Nomisma.org  took 157.54779767990112s
Accuracy | Check White space in annotation for Nomisma.org  took 2.716484785079956s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.36338996887207s
Consistency | Disjoint class check for Nomisma.org  took 0.38091564178466797s
Consistency | Check Misplaced properties for Nomisma.org  took 29.574625730514526s
Consistency | Check Ontology hijacking for Nomisma.org  took 162.82054138183594s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 2.0353946685791016s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 32.297510385513306s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.8759655952453613s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.6499283313751221s
Security | Sign check for Nomisma.org  took 0.35677218437194824s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1709.318246126175s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.6786880493164062s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.02170109748840332s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 6.461143493652344e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 2.384185791015625e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.3589859008789062e-05s
INFO | --- Analysis for nomisma_org took 8461.865479707718s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.33918094635009766s
Availability | VoID file availability check for Curriculum Vitae took 0.0005135536193847656s
Extra | Recovery of all triples for Curriculum Vitae took 0.9810070991516113s
Performance | Total latancy measurement for Curriculum Vitae took 1.012728214263916s
Amount of data | Number of triples check for Curriculum Vitae took 0.22845172882080078s
Interoperability | New terms check for Curriculum Vitae took 1.682344675064087s
Versatility | Languages check for Curriculum Vitae took 0.21157169342041016s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.2631521224975586s
Interpretability | RDF structures check for Curriculum Vitae took 0.16053438186645508s
Versatility | Serialization formats check for Curriculum Vitae took 0.1474010944366455s
Availability | RDF dump link check for Curriculum Vitae took 0.24022269248962402s
License | MR license check for Curriculum Vitae took 0.15443944931030273s
License | HR license check for Curriculum Vitae took 0.2382972240447998s
Amount of data | Number of property check for Curriculum Vitae took 0.12398123741149902s
Understandability | Number of label check for Curriculum Vitae took 0.2544426918029785s
Understandability | URI regex check for Curriculum Vitae took 0.25458240509033203s
Understandability | Vocabs check for Curriculum Vitae took 0.14279937744140625s
Verifiability | Authors check for Curriculum Vitae took 0.25236010551452637s
Verifiability | Publishers check for Curriculum Vitae took 0.1272430419921875s
Performance | Throughput check for Curriculum Vitae took 10.52096438407898s
Amount of data | Check the number of entities for Curriculum Vitae took 7.009506225585938e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.14610815048217773s
Interlinking | sameAs chians check for Curriculum Vitae took 0.14885902404785156s
Interlinking | skos check for Curriculum Vitae took 0.33527398109436035s
Interlinking | skos check for Curriculum Vitae took 0.15482783317565918s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.11796164512634277s
Currency | Creation date check for Curriculum Vitae took 0.29974961280822754s
Currency | Modification date check for Curriculum Vitae took 0.42374491691589355s
Rep.Conc. | URIs length for Curriculum Vitae took 0.37436842918395996s
Interoperability | New vocabularies check for Curriculum Vitae took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.1141350269317627s
Accuracy | Check Functional Property for Curriculum Vitae took 0.13384389877319336s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.11301112174987793s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.12265992164611816s
Accuracy | Check White space in annotation for Curriculum Vitae took 9.131431579589844e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.002112865447998047s
Consistency | Disjoint class check for Curriculum Vitae took 0.11768841743469238s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.38636279106140137s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.7182977199554443s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.6167197227478027s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.814281702041626s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0016238689422607422s
Security | Sign check for Curriculum Vitae took 0.23124074935913086s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 20.171793937683105s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.27469921112060547s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.0225222110748291s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.001135110855102539s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 2.384185791015625e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.3828277587890625e-05s
INFO | --- Analysis for Nordine_Bittich took 116.86665630340576s
Availability | SPARQL endpoint availability check for NorPark took 0.07764577865600586s
Availability | VoID file availability check for NorPark took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for NorPark took 0.300464391708374s
Reputation | Calculation of the PageRank for NorPark took 0.021358966827392578s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0008108615875244141s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.792213439941406e-05s
Believability | Calculation of trust value for NorPark took 8.106231689453125e-06s
INFO | --- Analysis for norpark took 2.8762996196746826s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.0260007381439209s
Availability | VoID file availability check for Parking Dataset took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.28576183319091797s
Reputation | Calculation of the PageRank for Parking Dataset took 0.021308422088623047s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.410743713378906e-05s
Believability | Calculation of trust value for Parking Dataset took 1.4066696166992188e-05s
INFO | --- Analysis for norpark2 took 2.6947600841522217s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.5914690494537354s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0005202293395996094s
Extra | Recovery of all triples for Norway fishery stocks dataset took 104.98385429382324s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9743919372558594s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.221571683883667s
Interoperability | New terms check for Norway fishery stocks dataset took 14.148257493972778s
Versatility | Languages check for Norway fishery stocks dataset took 300.1927900314331s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 1.8896362781524658s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.3316001892089844s
Versatility | Serialization formats check for Norway fishery stocks dataset took 6.912820339202881s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.2568318843841553s
License | MR license check for Norway fishery stocks dataset took 0.3255198001861572s
License | HR license check for Norway fishery stocks dataset took 300.1380376815796s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.21620392799377441s
Understandability | Number of label check for Norway fishery stocks dataset took 1.2493000030517578s
Understandability | URI regex check for Norway fishery stocks dataset took 0.8748509883880615s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.19266843795776367s
Verifiability | Authors check for Norway fishery stocks dataset took 0.21045494079589844s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2276782989501953s
Performance | Throughput check for Norway fishery stocks dataset took 11.171218395233154s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 3.2901763916015625e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.20426249504089355s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.22054600715637207s
Interlinking | skos check for Norway fishery stocks dataset took 0.5105509757995605s
Interlinking | skos check for Norway fishery stocks dataset took 0.39885544776916504s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 4.15828275680542s
Currency | Creation date check for Norway fishery stocks dataset took 0.46128106117248535s
Currency | Modification date check for Norway fishery stocks dataset took 0.23663115501403809s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 150.899240732193s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.22405099868774414s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.4976367950439453s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.1821281909942627s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 31.68308448791504s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.654418468475342s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.6090259552001953s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.18599319458007812s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 86.52073526382446s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.18329644203186s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 33.43429398536682s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.403998613357544s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 87.29822826385498s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.817146062850952s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5815021991729736s
Security | Sign check for Norway fishery stocks dataset took 0.5433917045593262s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 2.2138566970825195s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.4109983444213867s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.022598743438720703s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 4.291534423828125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.049041748046875e-05s
INFO | --- Analysis for Norway_Fishery_ took 2232.763351202011s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.8688466548919678s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.3067970275878906s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020661592483520508s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.649162292480469e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.1682510375976562e-05s
INFO | --- Analysis for norwegian-geo-divisions took 4.780278921127319s
Availability | SPARQL endpoint availability check for NITP took 8.511543273925781e-05s
Availability | VoID file availability check for NITP took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for NITP took 0.28235650062561035s
Reputation | Calculation of the PageRank for NITP took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for NITP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for NITP took 6.651878356933594e-05s
Believability | Calculation of trust value for NITP took 6.4373016357421875e-06s
INFO | --- Analysis for notIdentifier took 3.428126096725464s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.291534423828125e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0003829002380371094s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.29071044921875s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02081584930419922s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.647804260253906e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 5.4836273193359375e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.057678699493408s
Availability | SPARQL endpoint availability check for NPM took 4.3392181396484375e-05s
Availability | VoID file availability check for NPM took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for NPM took 0.45473265647888184s
Reputation | Calculation of the PageRank for NPM took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for NPM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for NPM took 3.218650817871094e-05s
Believability | Calculation of trust value for NPM took 1.1444091796875e-05s
INFO | --- Analysis for npm took 3.68289852142334s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.04334664344787598s
Availability | VoID file availability check for NTNU special collections took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.28577280044555664s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.435943603515625e-05s
Believability | Calculation of trust value for NTNU special collections took 8.106231689453125e-06s
INFO | --- Analysis for ntnusc took 5.440497875213623s
Availability | SPARQL endpoint availability check for links took 4.315376281738281e-05s
Availability | VoID file availability check for links took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for links took 0.30950403213500977s
Reputation | Calculation of the PageRank for links took 0.020433664321899414s
Interlinking | Calculation of Degree of Connection for links took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for links took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for links took 1.0967254638671875e-05s
Believability | Calculation of trust value for links took 1.2874603271484375e-05s
INFO | --- Analysis for nugmyanmar took 2.645249843597412s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.410743713378906e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0003116130828857422s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.31136131286621094s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00010180473327636719s
Believability | Calculation of trust value for NUTS (GeoVocab) took 8.58306884765625e-06s
INFO | --- Analysis for nuts-geovocab took 2.8605098724365234s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.4269406795501709s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0003662109375s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.3788111209869385s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.02024674415588379s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.747245788574219e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 6.4373016357421875e-06s
INFO | --- Analysis for nvd took 4.337435483932495s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.915473222732544s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.31427669525146484s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.939338684082031e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 6.198883056640625e-06s
INFO | --- Analysis for nvs took 8.655831336975098s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 5.173683166503906e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.29584670066833496s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.02309560775756836s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018405914306640625s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for nytimes-linked-open-data took 2.7480006217956543s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.8124649524688721s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006537437438964844s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.4127366542816162s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.8091590404510498s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 3.561957836151123s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7684476375579834s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.21046781539917s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 3.4199368953704834s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.2676081657409668s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.37463855743408203s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5423808097839355s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.5096645355224609s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.38858914375305176s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.24520301818848s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.3602571487426758s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.8603827953338623s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.7354140281677246s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.4762740135192871s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.38909244537353516s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.36724114418029785s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.164687395095825s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 3.457069396972656e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.36381030082702637s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.43250393867492676s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3851015567779541s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.29570484161376953s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.42882585525512695s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.8375208377838135s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.38517069816589355s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.767139196395874s
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.3843986988067627s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.34647583961486816s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.35509181022644043s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.794973611831665s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.031108856201171875s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.028049230575561523s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.5285248756408691s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.648841381072998s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.4637284278869629s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 1.9419443607330322s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.2447073459625244s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.43662714958191s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03345894813537598s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.4024062156677246s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.34200096130371094s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 1.1414339542388916s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.38166165351867676s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010633468627929688s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.3589859008789062e-05s
INFO | --- Analysis for ocd took 382.6647641658783s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.553794860839844e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2872273921966553s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.124641418457031e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.2636184692382812e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.5515570640563965s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 3.178863048553467s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.3085184097290039s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 7.772445678710938e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.0251998901367188e-05s
INFO | --- Analysis for oceandrilling-codices took 9.429121017456055s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 2.7648017406463623s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.29332852363586426s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.24249267578125e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.4781951904296875e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 7.4850990772247314s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 3.018092632293701s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2917907238006592s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.022211551666259766s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.266334533691406e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 2.47955322265625e-05s
INFO | --- Analysis for oceandrilling-forams took 7.832136869430542s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 2.685253381729126s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.2860589027404785s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02141594886779785s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.790855407714844e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 8.344650268554688e-06s
INFO | --- Analysis for oceandrilling-janus took 7.489528656005859s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.973475456237793s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0008540153503417969s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.28891444206237793s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 4.9591064453125e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.2874603271484375e-05s
INFO | --- Analysis for oceandrilling-janusamp took 18.34915590286255s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.0839569568634033s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0008137226104736328s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.299910306930542s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.022442340850830078s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.33514404296875e-05s
INFO | --- Analysis for oceandrilling-ldeo took 8.14110803604126s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.649162292480469e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.292832612991333s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 6.031990051269531e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 8.106231689453125e-06s
INFO | --- Analysis for oclc-fast took 9.030495643615723s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.601478576660156e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.28729939460754395s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.059906005859375e-06s
INFO | --- Analysis for odc-imd-environment-score took 6.004979133605957s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.21203303337097168s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.00036978721618652344s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.190955638885498s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 1.5044875144958496s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.22127270698547363s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.5563852787017822s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.48548126220703125s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.23938798904419s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.10967421531677246s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.13831806182861328s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.1530911922454834s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 50.71131253242493s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.16141796112060547s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.226794958114624s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.6577098369598389s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.2018136978149414s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.34325456619262695s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.14941906929016113s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.21574950218200684s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.21604275703430176s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 10.957483291625977s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 7.081031799316406e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.21138596534729004s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.2034773826599121s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.226637601852417s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.2129201889038086s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.15901565551757812s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.467742919921875s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.21400213241577148s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.7449235916137695s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.14098048210144043s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.2117304801940918s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.21265721321105957s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.21933674812316895s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.5418035984039307s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.2427222728729248s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.5465714931488037s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.0001480579376220703s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.3156766891479492s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.1590266227722168s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.34665346145629883s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020684003829956055s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.6716461181640625e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.6689300537109375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.245208740234375e-06s
INFO | --- Analysis for odc-lsoa took 265.9056324958801s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.10441803932189941s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.3150341510772705s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020952701568603516s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.942054748535156e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for oecd-linked-data took 2.9323720932006836s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.309539794921875s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.3333475589752197s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.021860599517822266s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 6.67572021484375e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.3589859008789062e-05s
INFO | --- Analysis for ogolod took 103.1831967830658s
Availability | SPARQL endpoint availability check for OLAC Metadata took 8.916854858398438e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.30304527282714844s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.0208737850189209s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.838539123535156e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.2636184692382812e-05s
INFO | --- Analysis for olac took 22.993262767791748s
Availability | SPARQL endpoint availability check for OLiA took 9.036064147949219e-05s
Availability | VoID file availability check for OLiA took 0.0008089542388916016s
Completeness | Calculation of interlinking completeness for OLiA took 0.3084874153137207s
Reputation | Calculation of the PageRank for OLiA took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012063980102539062s
Believability | Calculation of trust value for OLiA took 1.1205673217773438e-05s
INFO | --- Analysis for olia took 11.786105871200562s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.553794860839844e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0008065700531005859s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.31979918479919434s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020869731903076172s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.172325134277344e-05s
Believability | Calculation of trust value for OLiA Discourse took 8.58306884765625e-06s
INFO | --- Analysis for olia-discourse took 7.80103874206543s
Availability | SPARQL endpoint availability check for Open Land Use took 0.19653773307800293s
Availability | VoID file availability check for Open Land Use took 0.0005257129669189453s
Extra | Recovery of all triples for Open Land Use took 107.80604386329651s
Performance | Total latancy measurement for Open Land Use took 0.9711692333221436s
Amount of data | Number of triples check for Open Land Use took 8.900006294250488s
Interoperability | New terms check for Open Land Use took 14.217678785324097s
Versatility | Languages check for Open Land Use took 300.2282073497772s
Interpretability | Number of blank nodes check for Open Land Use took 1.9549140930175781s
Interpretability | RDF structures check for Open Land Use took 0.19969654083251953s
Versatility | Serialization formats check for Open Land Use took 8.460902214050293s
Availability | RDF dump link check for Open Land Use took 0.21919035911560059s
License | MR license check for Open Land Use took 0.18301630020141602s
License | HR license check for Open Land Use took 300.2077901363373s
Amount of data | Number of property check for Open Land Use took 0.21294617652893066s
Understandability | Number of label check for Open Land Use took 1.372370719909668s
Understandability | URI regex check for Open Land Use took 0.8081028461456299s
Understandability | Vocabs check for Open Land Use took 0.21317219734191895s
Verifiability | Authors check for Open Land Use took 0.18164420127868652s
Verifiability | Publishers check for Open Land Use took 0.23804020881652832s
Performance | Throughput check for Open Land Use took 11.401458501815796s
Amount of data | Check the number of entities for Open Land Use took 8.034706115722656e-05s
Verifiability | Contribs. check for Open Land Use took 0.21158194541931152s
Interlinking | sameAs chians check for Open Land Use took 0.2041771411895752s
Interlinking | skos check for Open Land Use took 0.4116706848144531s
Interlinking | skos check for Open Land Use took 0.41225385665893555s
Timeliness | dataset update frequency check for Open Land Use took 4.1893696784973145s
Currency | Creation date check for Open Land Use took 0.5094203948974609s
Currency | Modification date check for Open Land Use took 0.21666288375854492s
Rep.Conc. | URIs length for Open Land Use took 157.31578946113586s
Interoperability | New vocabularies check for Open Land Use took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.3537101745605469s
Accuracy | Check Functional Property for Open Land Use took 0.5685696601867676s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.5198361873626709s
Accuracy | Check Empty annotation labels for Open Land Use took 41.27570962905884s
Accuracy | Check White space in annotation for Open Land Use took 2.663527727127075s
Accuracy | Check Datatype consistency for Open Land Use took 2.6283013820648193s
Consistency | Disjoint class check for Open Land Use took 0.17795515060424805s
Consistency | Check Misplaced properties for Open Land Use took 86.05526065826416s
Consistency | Misplaced classes for Open Land Use took 8.193345308303833s
Consistency | Check Ontology hijacking for Open Land Use took 32.738080978393555s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.3322405815124512s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 87.0668773651123s
Conciseness | Check Extensional conciseness for Open Land Use took 2.8342506885528564s
Conciseness | Check Intensional conciseness for Open Land Use took 0.5220415592193604s
Security | Sign check for Open Land Use took 0.22025728225708008s
Availability | Check URIs Dereferenciability for Open Land Use took 1.3175606727600098s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.7773487567901611s
Reputation | Calculation of the PageRank for Open Land Use took 0.020975112915039062s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Land Use took 1.2636184692382812e-05s
INFO | --- Analysis for OLU took 2243.0482325553894s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.7018659114837646s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.33260202407836914s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0207669734954834s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.267692565917969e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-als took 3.956772804260254s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.24458837509155273s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.3050229549407959s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.021345138549804688s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-arb took 3.3637471199035645s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.23755502700805664s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2995302677154541s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-bul took 3.342216730117798s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2915644645690918s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2899782657623291s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-cow took 3.5144436359405518s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.30191540718078613s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.33537769317626953s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-cwn took 3.3708627223968506s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.26103997230529785s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.3016326427459717s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.02174544334411621s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007147789001464844s
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 1.0251998901367188e-05s
INFO | --- Analysis for omwn-dan took 3.356581926345825s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.25425076484680176s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.30957794189453125s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020939350128173828s
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.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-ell took 5.7370076179504395s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2787008285522461s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.31000590324401855s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-eng took 3.4191248416900635s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.266340970993042s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.28357863426208496s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-fas took 3.389317512512207s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2753932476043701s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.3376891613006592s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.022350549697875977s
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.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-fin took 3.4466869831085205s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.30378198623657227s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.30618786811828613s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.02183818817138672s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-fra took 3.4994733333587646s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2890350818634033s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.27224111557006836s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.8160552978515625e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-heb took 3.3433260917663574s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.26465868949890137s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2873837947845459s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-hrv took 3.3869082927703857s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2631368637084961s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.287853479385376s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.02217555046081543s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-isl took 3.344114065170288s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.25100278854370117s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.3052399158477783s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.021797895431518555s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-ita took 3.449538469314575s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2638564109802246s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2848246097564697s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-iwn took 3.3143198490142822s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.24236679077148438s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.30573105812072754s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-jpn took 3.3118374347686768s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.24970364570617676s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2968912124633789s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-mcr took 3.362722873687744s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2462141513824463s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2774660587310791s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.021129131317138672s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-msa took 3.4458730220794678s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.28859734535217285s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.2885162830352783s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02185654640197754s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-nld took 3.335141658782959s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.249342679977417s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.28215885162353516s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-nor took 3.3595805168151855s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2546660900115967s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.27577853202819824s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-pol took 3.284456729888916s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.25292396545410156s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.25792694091796875s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-por took 3.2046315670013428s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.256105899810791s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.29909539222717285s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.02091050148010254s
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.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-ron took 3.3054869174957275s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.24179577827453613s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2891979217529297s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-slk took 3.328355312347412s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2866356372833252s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.29140615463256836s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-slv took 3.297903060913086s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2469949722290039s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2832961082458496s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-swe took 3.3683042526245117s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.24330830574035645s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.3137509822845459s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.02133631706237793s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-tha took 3.4849579334259033s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 5.352903366088867s
Availability | VoID file availability check for OntoBeef Domain took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.32225823402404785s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.553794860839844e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.1682510375976562e-05s
INFO | --- Analysis for ontobeef-domain took 28.88908052444458s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.3184800148010254s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02095508575439453s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0009315013885498047s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 0.00010347366333007812s
Believability | Calculation of trust value for Ontos News Portal took 1.1444091796875e-05s
INFO | --- Analysis for ontos-news-portal took 6.546904563903809s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.553794860839844e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.3000659942626953s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 2.9325485229492188e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.1920928955078125e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 2.9033238887786865s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 9.441375732421875e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.28720760345458984s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.021457672119140625s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.5762786865234375e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.4066696166992188e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 11.093355178833008s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 9.775161743164062e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.3174600601196289s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.696846008300781e-05s
Believability | Calculation of trust value for Open Data Euskadi took 9.059906005859375e-06s
INFO | --- Analysis for open-data-euskadi took 8.49166202545166s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 9.083747863769531e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0007531642913818359s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.29730892181396484s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.022051095962524414s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 9.870529174804688e-05s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.2874603271484375e-05s
INFO | --- Analysis for open-data-risp took 6.872653245925903s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.20490717887878418s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006775856018066406s
Extra | Recovery of all triples for Open Data Thesaurus took 1.0779774188995361s
Performance | Total latancy measurement for Open Data Thesaurus took 0.46743297576904297s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1262814998626709s
Interoperability | New terms check for Open Data Thesaurus took 1.3610115051269531s
Versatility | Languages check for Open Data Thesaurus took 0.12717366218566895s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.11903619766235352s
Security | Check HTTPS for Open Data Thesaurus took 0.3097231388092041s
Interpretability | RDF structures check for Open Data Thesaurus took 0.11432099342346191s
Versatility | Serialization formats check for Open Data Thesaurus took 0.11251091957092285s
Availability | RDF dump link check for Open Data Thesaurus took 1.0800316333770752s
License | MR license check for Open Data Thesaurus took 0.12848997116088867s
License | HR license check for Open Data Thesaurus took 0.09044599533081055s
Amount of data | Number of property check for Open Data Thesaurus took 0.12050819396972656s
Understandability | Number of label check for Open Data Thesaurus took 0.11359667778015137s
Understandability | URI regex check for Open Data Thesaurus took 0.16808390617370605s
Understandability | Vocabs check for Open Data Thesaurus took 0.12659096717834473s
Verifiability | Authors check for Open Data Thesaurus took 0.11228585243225098s
Verifiability | Publishers check for Open Data Thesaurus took 0.11837601661682129s
Performance | Throughput check for Open Data Thesaurus took 10.531849145889282s
Amount of data | Check the number of entities for Open Data Thesaurus took 8.392333984375e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.1273343563079834s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.11794281005859375s
Interlinking | skos check for Open Data Thesaurus took 0.12115168571472168s
Interlinking | skos check for Open Data Thesaurus took 0.0872337818145752s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.09455060958862305s
Currency | Creation date check for Open Data Thesaurus took 0.17876410484313965s
Currency | Modification date check for Open Data Thesaurus took 0.20751953125s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.45868754386901855s
Interoperability | New vocabularies check for Open Data Thesaurus took 0.8074114322662354s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11194968223571777s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.07912397384643555s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.07835674285888672s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.17697477340698242s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011296272277832031s
Consistency | Disjoint class check for Open Data Thesaurus took 0.09486818313598633s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.1732029914855957s
Consistency | Misplaced classes for Open Data Thesaurus took 0.08808255195617676s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.4068450927734375s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.322540044784546s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00014328956604003906s
Security | Sign check for Open Data Thesaurus took 0.08576178550720215s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.31116294860839844s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.01992964744567871s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.772445678710938e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.6649935245513916s
Believability | Calculation of trust value for Open Data Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for open-data-thesaurus took 93.60602235794067s
Availability | SPARQL endpoint availability check for Open Election Data Project took 8.749961853027344e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.36945557594299316s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.604194641113281e-05s
Believability | Calculation of trust value for Open Election Data Project took 1.0013580322265625e-05s
INFO | --- Analysis for open-election-data-project took 42.870081424713135s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.607820987701416s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.3192782402038574s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02173614501953125s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 9.179115295410156e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 9.059906005859375e-06s
INFO | --- Analysis for open-energy-info-wiki took 20.689356088638306s
Availability | SPARQL endpoint availability check for Open Library took 8.606910705566406e-05s
Availability | VoID file availability check for Open Library took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Open Library took 0.31591033935546875s
Reputation | Calculation of the PageRank for Open Library took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for Open Library took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Open Library took 8.749961853027344e-05s
Believability | Calculation of trust value for Open Library took 1.0728836059570312e-05s
INFO | --- Analysis for open-library took 13.727790117263794s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.18161344528198242s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0004699230194091797s
Extra | Recovery of all triples for Open Land Use @PSNC took 111.52719688415527s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9555714130401611s
Amount of data | Number of triples check for Open Land Use @PSNC took 8.803824424743652s
Interoperability | New terms check for Open Land Use @PSNC took 14.0132896900177s
Versatility | Languages check for Open Land Use @PSNC took 300.1698422431946s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.142462968826294s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.22110629081726074s
Versatility | Serialization formats check for Open Land Use @PSNC took 6.610468626022339s
Availability | RDF dump link check for Open Land Use @PSNC took 0.2097616195678711s
License | MR license check for Open Land Use @PSNC took 0.21254825592041016s
License | HR license check for Open Land Use @PSNC took 300.2096974849701s
Amount of data | Number of property check for Open Land Use @PSNC took 0.22564053535461426s
Understandability | Number of label check for Open Land Use @PSNC took 1.3693468570709229s
Understandability | URI regex check for Open Land Use @PSNC took 0.4267005920410156s
Understandability | Vocabs check for Open Land Use @PSNC took 0.20485305786132812s
Verifiability | Authors check for Open Land Use @PSNC took 0.2128615379333496s
Verifiability | Publishers check for Open Land Use @PSNC took 0.24542832374572754s
Performance | Throughput check for Open Land Use @PSNC took 11.037595510482788s
Amount of data | Check the number of entities for Open Land Use @PSNC took 7.796287536621094e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.2010350227355957s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.2014327049255371s
Interlinking | skos check for Open Land Use @PSNC took 0.41138267517089844s
Interlinking | skos check for Open Land Use @PSNC took 0.3973042964935303s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 4.431570529937744s
Currency | Creation date check for Open Land Use @PSNC took 0.47916483879089355s
Currency | Modification date check for Open Land Use @PSNC took 0.2296285629272461s
Rep.Conc. | URIs length for Open Land Use @PSNC took 150.9653356075287s
Interoperability | New vocabularies check for Open Land Use @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.21320319175720215s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.1785721778869629s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.19545412063598633s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 32.58514094352722s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.665679693222046s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.590191602706909s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.2014155387878418s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 86.26342964172363s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.174367666244507s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 30.40075945854187s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.3866169452667236s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 87.34366226196289s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.815953254699707s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.5773477554321289s
Security | Sign check for Open Land Use @PSNC took 0.560016393661499s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 15.404749155044556s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.5473051071166992s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.0209810733795166s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 3.0994415283203125e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Open_Land_Use took 2239.782513141632s
Availability | SPARQL endpoint availability check for flyatlas took 1.6047554016113281s
Availability | VoID file availability check for flyatlas took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for flyatlas took 0.27898073196411133s
Reputation | Calculation of the PageRank for flyatlas took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for flyatlas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for flyatlas took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.0279159545898438e-05s
Believability | Calculation of trust value for flyatlas took 1.3113021850585938e-05s
INFO | --- Analysis for openbiomed-flyatlas took 6.014573335647583s
Availability | SPARQL endpoint availability check for OpenCalais took 4.315376281738281e-05s
Availability | VoID file availability check for OpenCalais took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.29306530952453613s
Reputation | Calculation of the PageRank for OpenCalais took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for OpenCalais took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010633468627929688s
Believability | Calculation of trust value for OpenCalais took 1.33514404296875e-05s
INFO | --- Analysis for opencalais took 6.940518856048584s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 9.083747863769531e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.3140099048614502s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.724761962890625e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 9.059906005859375e-06s
INFO | --- Analysis for opencorporates took 3.0746045112609863s
Availability | SPARQL endpoint availability check for OpenCyc took 8.749961853027344e-05s
Availability | VoID file availability check for OpenCyc took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2968027591705322s
Reputation | Calculation of the PageRank for OpenCyc took 0.02102971076965332s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010514259338378906s
Believability | Calculation of trust value for OpenCyc took 8.106231689453125e-06s
INFO | --- Analysis for opencyc took 2.660569906234741s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.2791919708251953s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.022032499313354492s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.5762786865234375e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.8024818897247314s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 8.821487426757812e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.29124021530151367s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02090167999267578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007143020629882812s
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 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 4.248681306838989s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 9.012222290039062e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0016322135925292969s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.2886030673980713s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.4729604721069336s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.300091028213501s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.6441619396209717s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 0.00011181831359863281s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2804841995239258s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.227365493774414s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 5.221366882324219e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.28240132331848145s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.021192550659179688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0009737014770507812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 3.29645037651062s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 8.869171142578125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.3194401264190674s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.081851005554199s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0003819465637207031s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.32318878173828125s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.6759772300720215s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 7.200241088867188e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0008039474487304688s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.3182387351989746s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.211517095565796s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 0.00010919570922851562s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.31783032417297363s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.022330760955810547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 3.4648079872131348s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 8.702278137207031e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2933773994445801s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0010406970977783203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.643986701965332s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 0.00011086463928222656s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0013670921325683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.3217732906341553s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.7488951683044434s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 9.202957153320312e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.27419400215148926s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.4246089458465576s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 5.53131103515625e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.31270503997802734s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02171015739440918s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.7496144771575928s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 8.7738037109375e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.30906176567077637s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02234053611755371s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 3.588629961013794s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 9.274482727050781e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.31536006927490234s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.5656914710998535s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.00010991096496582031s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.3002910614013672s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.8611814975738525s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 9.1552734375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.3406834602355957s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02298569679260254s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.378117322921753s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 8.702278137207031e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2743043899536133s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.6725823879241943s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2778923511505127s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02339458465576172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.5152931213378906s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 8.988380432128906e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.30281782150268555s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.02332305908203125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.4534006118774414s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 9.036064147949219e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.28864169120788574s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.021799802780151367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 3.1031711101531982s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 9.250640869140625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.40028834342956543s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.022125959396362305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 3.861083984375s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.001508474349975586s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.3296844959259033s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.022639989852905273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 3.5279123783111572s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 9.107589721679688e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2978708744049072s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.905993700027466s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 9.250640869140625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0008203983306884766s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.3191070556640625s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02101445198059082s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.102865695953369s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.673004150390625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007104873657226562s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.27960848808288574s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.224959373474121s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.00010180473327636719s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.00081634521484375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.33076977729797363s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.905942440032959s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.1552734375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.299879789352417s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 3.1060619354248047s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.726119995117188e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.3263707160949707s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.9474878311157227s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 8.630752563476562e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2870218753814697s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.02088475227355957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.657322883605957s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 5.245208740234375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007612705230712891s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.30861520767211914s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.160754442214966s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.7206878662109375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.27817416191101074s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.021630287170410156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.085716485977173s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.678436279296875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.29147911071777344s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.021010637283325195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.245208740234375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.620893716812134s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.3410770893096924s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.023476362228393555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0010368824005126953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 5.841255187988281e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.714073419570923s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.00010347366333007812s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.26332855224609375s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.653670310974121s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.036064147949219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.3286409378051758s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.022524118423461914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.52587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0010399818420410156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 5.8650970458984375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.1390631198883057s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.32430362701416016s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.021197080612182617s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 4.3496692180633545s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2980217933654785s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.021021127700805664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 9.775161743164062e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.3601233959198s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.649162292480469e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.3258178234100342s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.021234512329101562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007231235504150391s
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 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.063603401184082s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.821487426757812e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2869691848754883s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.2551496028900146s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.749961853027344e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2857201099395752s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.021036624908447266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.1971395015716553s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 5.364418029785156e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.30776476860046387s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02203965187072754s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 3.0857760906219482s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.035322427749634s
Availability | VoID file availability check for Open Data of Ecuador took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.29567766189575195s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.02109241485595703s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 0.00010323524475097656s
Believability | Calculation of trust value for Open Data of Ecuador took 1.430511474609375e-05s
INFO | --- Analysis for opendataec took 10.591547966003418s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 9.679794311523438e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.308910608291626s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.02179694175720215s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 11.017544746398926s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 6.318092346191406e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2690896987915039s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02192997932434082s
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.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.0967254638671875e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.030673027038574s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 5.173683166503906e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2754673957824707s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.049041748046875e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.8258354663848877s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 8.845329284667969e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.30081987380981445s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.021585702896118164s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.33514404296875e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.742877244949341s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 0.00010704994201660156s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.2676424980163574s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020869016647338867s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.52587890625e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.7488715648651123s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 5.507469177246094e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0003230571746826172s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.29868388175964355s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02147960662841797s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.0967254638671875e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.236618757247925s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 0.00015282630920410156s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2975451946258545s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020889759063720703s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0008292198181152344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.1682510375976562e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.715733051300049s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 0.00010800361633300781s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2793424129486084s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020900487899780273s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.1444091796875e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.657111644744873s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.458427429199219e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.3397965431213379s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02098703384399414s
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.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 5.7220458984375e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.753948211669922s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.628878831863403s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.27570676803588867s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.02195906639099121s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.5762786865234375e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.0728836059570312e-05s
INFO | --- Analysis for openlink-lod-cache took 63.38056516647339s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 8.893013000488281e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.28573036193847656s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02210688591003418s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.703636169433594e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.049041748046875e-05s
INFO | --- Analysis for openlinksw-dataspaces took 3.522427558898926s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 8.893013000488281e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.00031757354736328125s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.3059215545654297s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.022974491119384766s
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.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.179115295410156e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 8.106231689453125e-06s
INFO | --- Analysis for openlylocal took 7.2029948234558105s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.3085739612579346s
Availability | VoID file availability check for OpenMobileNetwork took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.28937458992004395s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.462501525878906e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.0728836059570312e-05s
INFO | --- Analysis for openmobilenetwork took 4.948822259902954s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.0312540531158447s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0007600784301757812s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.27914905548095703s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.022118091583251953s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.00010061264038085938s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 6.116913557052612s
Availability | SPARQL endpoint availability check for oreilly took 8.845329284667969e-05s
Availability | VoID file availability check for oreilly took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for oreilly took 0.30347681045532227s
Reputation | Calculation of the PageRank for oreilly took 0.02250361442565918s
Interlinking | Calculation of Degree of Connection for oreilly took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.435943603515625e-05s
Believability | Calculation of trust value for oreilly took 9.775161743164062e-06s
INFO | --- Analysis for oreilly took 4.856497526168823s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.4285337924957275s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.28801512718200684s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.02272176742553711s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.6716461181640625e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.3828277587890625e-05s
INFO | --- Analysis for Organchem-Data took 7.470022678375244s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.06923818588256836s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2760779857635498s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.224082946777344e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 5.245208740234375e-06s
INFO | --- Analysis for organic-edunet took 9.549856901168823s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.41518330574035645s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005352497100830078s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 5.966956853866577s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.70802903175354s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.14515471458435059s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.5998685359954834s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 5.692274808883667s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.13356852531433105s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.3844175338745117s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.1501171588897705s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.13865089416503906s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.14648771286010742s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.274059295654297s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.15584397315979004s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.17251968383789062s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.3202509880065918s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.15430259704589844s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.15245437622070312s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.15768766403198242s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.589892148971558s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 6.914138793945312e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.1783139705657959s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.13386106491088867s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16704249382019043s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.14237022399902344s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.12585663795471191s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.30213165283203125s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.3074533939361572s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 3.7806761264801025s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.13098382949829102s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.1946113109588623s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.18419504165649414s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.4994852542877197s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.2974984645843506s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2737915515899658s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.25005507469177246s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.2890474796295166s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.854583740234375s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.182326316833496s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.319603681564331s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.0693411827087402s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.29696178436279297s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.1835787296295166s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.160353422164917s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2016.1342389583588s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.4951045513153076s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.022621631622314453s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 2.2411346435546875e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 4.8160552978515625e-05s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.1205673217773438e-05s
INFO | --- Analysis for orkg took 2247.5301852226257s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.062263250350952s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.309694766998291s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.021880149841308594s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 9.036064147949219e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.0013580322265625e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 29.32786250114441s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.5547990798950195s
Availability | VoID file availability check for OSM Semantic Network took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.27765750885009766s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.022377729415893555s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.933906555175781e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.33514404296875e-05s
INFO | --- Analysis for osm-semantic-network took 8.490724563598633s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.31636619567871094s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00047659873962402344s
Extra | Recovery of all triples for Open Transport Map @PSNC took 113.35641860961914s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.9986550807952881s
Amount of data | Number of triples check for Open Transport Map @PSNC took 8.937969446182251s
Interoperability | New terms check for Open Transport Map @PSNC took 14.0284423828125s
Versatility | Languages check for Open Transport Map @PSNC took 300.2244942188263s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 2.0328052043914795s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.20933914184570312s
Versatility | Serialization formats check for Open Transport Map @PSNC took 7.285382986068726s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.20723915100097656s
License | MR license check for Open Transport Map @PSNC took 0.671806812286377s
License | HR license check for Open Transport Map @PSNC took 300.2153809070587s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.22048377990722656s
Understandability | Number of label check for Open Transport Map @PSNC took 1.453442096710205s
Understandability | URI regex check for Open Transport Map @PSNC took 0.3784303665161133s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.48840975761413574s
Verifiability | Authors check for Open Transport Map @PSNC took 0.2061154842376709s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.2583589553833008s
Performance | Throughput check for Open Transport Map @PSNC took 11.247636795043945s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 9.250640869140625e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.202894926071167s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.18834614753723145s
Interlinking | skos check for Open Transport Map @PSNC took 0.42101407051086426s
Interlinking | skos check for Open Transport Map @PSNC took 0.41395139694213867s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 3.988187789916992s
Currency | Creation date check for Open Transport Map @PSNC took 0.4740121364593506s
Currency | Modification date check for Open Transport Map @PSNC took 0.23798894882202148s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 148.58092641830444s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.18350982666015625s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.4167954921722412s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.19576478004455566s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 35.77960991859436s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.6957874298095703s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.6195740699768066s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.1970043182373047s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 86.20449185371399s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.298809051513672s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 32.833516120910645s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.3417906761169434s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 86.71432638168335s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.8223531246185303s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.5457315444946289s
Security | Sign check for Open Transport Map @PSNC took 0.20031404495239258s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 13.277024269104004s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.6450018882751465s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.02194976806640625s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for OTM took 2249.4977927207947s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.692012071609497s
Availability | VoID file availability check for Pali English Lexicon took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.29364752769470215s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.021423816680908203s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 4.172325134277344e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.1682510375976562e-05s
INFO | --- Analysis for pali-english-lexicon took 7.783232688903809s
Availability | SPARQL endpoint availability check for PanLex took 1.9645733833312988s
Availability | VoID file availability check for PanLex took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for PanLex took 0.28487348556518555s
Reputation | Calculation of the PageRank for PanLex took 0.021373987197875977s
Interlinking | Calculation of Degree of Connection for PanLex took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0008311271667480469s
Interlinking | Calculation of Clustering coefficient for PanLex took 8.392333984375e-05s
Believability | Calculation of trust value for PanLex took 1.33514404296875e-05s
INFO | --- Analysis for panlex took 4.789979934692383s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 7.891654968261719e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.3906669616699219s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020880699157714844s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.933906555175781e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0967254638671875e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 6.072232246398926s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.05828738212585449s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.32994818687438965s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.021641969680786133s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.982948303222656e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.8952982425689697s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 9.918212890625e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.29817700386047363s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.933906555175781e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.049041748046875e-05s
INFO | --- Analysis for pdev-lemon took 4.224437713623047s
Availability | SPARQL endpoint availability check for pdevlemon took 8.916854858398438e-05s
Availability | VoID file availability check for pdevlemon took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.30559444427490234s
Reputation | Calculation of the PageRank for pdevlemon took 0.0219266414642334s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.314018249511719e-05s
Believability | Calculation of trust value for pdevlemon took 1.0728836059570312e-05s
INFO | --- Analysis for pdevlemon took 3.375675678253174s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.5299530029296875e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.28806424140930176s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.082389831542969e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.0251998901367188e-05s
INFO | --- Analysis for periodo took 19.67207932472229s
Availability | SPARQL endpoint availability check for Personal_Homepages took 8.726119995117188e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.30495524406433105s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.022385835647583008s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0003783702850341797s
Believability | Calculation of trust value for Personal_Homepages took 1.0251998901367188e-05s
INFO | --- Analysis for personal-homepages took 2.708970069885254s
Availability | SPARQL endpoint availability check for Ontology of University People took 8.7738037109375e-05s
Availability | VoID file availability check for Ontology of University People took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.26416802406311035s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.314018249511719e-05s
Believability | Calculation of trust value for Ontology of University People took 1.1205673217773438e-05s
INFO | --- Analysis for PersonOnto took 2.712301015853882s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.927618980407715s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2822682857513428s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.021355390548706055s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2636184692382812e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 5.4836273193359375e-06s
INFO | --- Analysis for PFKHS took 8.95017695426941s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.204378366470337s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.3304009437561035s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02241802215576172s
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.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1205673217773438e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3113021850585938e-05s
INFO | --- Analysis for PFRPPH took 7.730538845062256s
Availability | SPARQL endpoint availability check for PGxLOD took 0.47050976753234863s
Availability | VoID file availability check for PGxLOD took 0.0006647109985351562s
Extra | Recovery of all triples for PGxLOD took 1.7640972137451172s
Performance | Total latancy measurement for PGxLOD took 0.8760809898376465s
Amount of data | Number of triples check for PGxLOD took 3.215771198272705s
Interoperability | New terms check for PGxLOD took 1.9177868366241455s
Versatility | Languages check for PGxLOD took 60.24271059036255s
Interpretability | Number of blank nodes check for PGxLOD took 1.5280745029449463s
Interpretability | RDF structures check for PGxLOD took 0.5355792045593262s
Versatility | Serialization formats check for PGxLOD took 0.35735225677490234s
Availability | RDF dump link check for PGxLOD took 16.851788997650146s
License | MR license check for PGxLOD took 0.816741943359375s
License | HR license check for PGxLOD took 64.16241955757141s
Amount of data | Number of property check for PGxLOD took 0.18961238861083984s
Understandability | Number of label check for PGxLOD took 2.9000515937805176s
Understandability | URI regex check for PGxLOD took 0.44557809829711914s
Understandability | Vocabs check for PGxLOD took 0.39575695991516113s
Verifiability | Authors check for PGxLOD took 0.5032765865325928s
Verifiability | Publishers check for PGxLOD took 0.3150022029876709s
Performance | Throughput check for PGxLOD took 10.95388650894165s
Amount of data | Check the number of entities for PGxLOD took 0.1193850040435791s
Verifiability | Contribs. check for PGxLOD took 0.15401649475097656s
Interlinking | sameAs chians check for PGxLOD took 0.2707693576812744s
Interlinking | skos check for PGxLOD took 1.8102543354034424s
Interlinking | skos check for PGxLOD took 0.22205281257629395s
Timeliness | dataset update frequency check for PGxLOD took 0.38727784156799316s
Currency | Creation date check for PGxLOD took 0.556502103805542s
Currency | Modification date check for PGxLOD took 0.3367292881011963s
Rep.Conc. | URIs length for PGxLOD took 6.869494915008545s
Interoperability | New vocabularies check for PGxLOD took 5.3656980991363525s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.16611647605895996s
Accuracy | Check Functional Property for PGxLOD took 0.18220138549804688s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.2088916301727295s
Accuracy | Check Empty annotation labels for PGxLOD took 1.12799072265625s
Accuracy | Check White space in annotation for PGxLOD took 0.03717660903930664s
Accuracy | Check Datatype consistency for PGxLOD took 0.028162479400634766s
Consistency | Disjoint class check for PGxLOD took 0.3131420612335205s
Consistency | Check Misplaced properties for PGxLOD took 6.557371139526367s
Consistency | Misplaced classes for PGxLOD took 0.3034367561340332s
Consistency | Check Ontology hijacking for PGxLOD took 1.872267723083496s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.2416868209838867s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.153196573257446s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03289222717285156s
Conciseness | Check Intensional conciseness for PGxLOD took 0.23970866203308105s
Security | Sign check for PGxLOD took 0.16596174240112305s
Availability | Check URIs Dereferenciability for PGxLOD took 2399.6350383758545s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.5411777496337891s
Reputation | Calculation of the PageRank for PGxLOD took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 5.5336833000183105s
Believability | Calculation of trust value for PGxLOD took 1.3589859008789062e-05s
INFO | --- Analysis for PGxLOD took 3670.4173414707184s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1211791038513184s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.26391005516052246s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.743171691894531e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0251998901367188e-05s
INFO | --- Analysis for phoible took 5.022076368331909s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 9.083747863769531e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.3037550449371338s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.021017789840698242s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.4332275390625e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.0967254638671875e-05s
INFO | --- Analysis for PISM took 15.999098062515259s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.601478576660156e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.3090395927429199s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.021846532821655273s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.58306884765625e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.4066696166992188e-05s
INFO | --- Analysis for planetdata-project-wiki took 2.7052340507507324s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.2417268753051758s
Availability | VoID file availability check for digitized plant specimen took 0.00030159950256347656s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.31365060806274414s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.022786617279052734s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.52587890625e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 9.202957153320312e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.3113021850585938e-05s
INFO | --- Analysis for plant-specimen took 4.000128269195557s
Availability | SPARQL endpoint availability check for Pleiades took 4.7206878662109375e-05s
Availability | VoID file availability check for Pleiades took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Pleiades took 0.2788715362548828s
Reputation | Calculation of the PageRank for Pleiades took 0.021022558212280273s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.940696716308594e-05s
Believability | Calculation of trust value for Pleiades took 1.3828277587890625e-05s
INFO | --- Analysis for pleiades took 14.357837915420532s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 9.036064147949219e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0009407997131347656s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.3104424476623535s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.647804260253906e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.1682510375976562e-05s
INFO | --- Analysis for podorozhnyk took 3.4206902980804443s
Availability | SPARQL endpoint availability check for Poképédia took 9.012222290039062e-05s
Availability | VoID file availability check for Poképédia took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2960324287414551s
Reputation | Calculation of the PageRank for Poképédia took 0.022095441818237305s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.581710815429688e-05s
Believability | Calculation of trust value for Poképédia took 1.1682510375976562e-05s
INFO | --- Analysis for pokepedia-fr took 2.875077247619629s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 6.151199340820312e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.3199160099029541s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.021717548370361328s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.058547973632812e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.2874603271484375e-05s
INFO | --- Analysis for polymath-virtual-library took 6.005988121032715s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2909519672393799s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007166862487792969s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 11.136858701705933s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6926257610321045s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.4566328525543213s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6411833763122559s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.314671516418457s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.38359713554382324s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.14725279808044434s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13741016387939453s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13653087615966797s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13738608360290527s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6305253505706787s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1442725658416748s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.185760498046875s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2641003131866455s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13643550872802734s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12855958938598633s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.14361166954040527s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.857986211776733s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.961822509765625e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13652324676513672s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13695812225341797s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.14348578453063965s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13690614700317383s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12936973571777344s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.27435874938964844s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.27454519271850586s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.435070991516113s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1387803554534912s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13483190536499023s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12824797630310059s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2573902606964111s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19630217552185059s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.7193126678466797s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.14479494094848633s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.8342390060424805s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.4726221561431885s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.296515703201294s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.0757107734680176s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.5694687366485596s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1353452205657959s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4934.235824108124s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.7848916053771973s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.021289348602294922s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 8.916854858398438e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6689300537109375e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 9.775161743164062e-06s
INFO | --- Analysis for portuguese_prisons_releases took 5187.412827253342s
Availability | SPARQL endpoint availability check for prefix.cc took 4.1961669921875e-05s
Availability | VoID file availability check for prefix.cc took 0.000457763671875s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2950775623321533s
Reputation | Calculation of the PageRank for prefix.cc took 0.021287918090820312s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.029273986816406e-05s
Believability | Calculation of trust value for prefix.cc took 1.0728836059570312e-05s
INFO | --- Analysis for prefix-cc took 3.361790895462036s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.595888614654541s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.30591678619384766s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02118682861328125s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.9591064453125e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.049041748046875e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 7.673093557357788s
Availability | SPARQL endpoint availability check for PreLex took 6.786407709121704s
Availability | VoID file availability check for PreLex took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for PreLex took 0.27673983573913574s
Reputation | Calculation of the PageRank for PreLex took 0.02095794677734375s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.915496826171875e-05s
Believability | Calculation of trust value for PreLex took 1.1444091796875e-05s
INFO | --- Analysis for prelex took 19.79861354827881s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.3553128242492676s
Availability | VoID file availability check for Prelinger Archives took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.28650379180908203s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.24249267578125e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.0728836059570312e-05s
INFO | --- Analysis for prelinger_archives took 12.553847789764404s
Availability | SPARQL endpoint availability check for PreMOn took 0.5837602615356445s
Availability | VoID file availability check for PreMOn took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for PreMOn took 0.2973601818084717s
Reputation | Calculation of the PageRank for PreMOn took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for PreMOn took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for PreMOn took 5.221366882324219e-05s
Believability | Calculation of trust value for PreMOn took 1.0967254638671875e-05s
INFO | --- Analysis for premon took 5.508054494857788s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 8.606910705566406e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.27733826637268066s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.555152893066406e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.049041748046875e-05s
INFO | --- Analysis for princeton-library-findingaids took 4.281689405441284s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.676821231842041s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.2740042209625244s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.021432876586914062s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for PrinParLat took 4.763951539993286s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.4273500442504883s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.2892639636993408s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.106231689453125e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 3.4189975261688232s
Availability | SPARQL endpoint availability check for Prior Panel took 8.893013000488281e-05s
Availability | VoID file availability check for Prior Panel took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.29075169563293457s
Reputation | Calculation of the PageRank for Prior Panel took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.457069396972656e-05s
Believability | Calculation of trust value for Prior Panel took 1.049041748046875e-05s
INFO | --- Analysis for Prior_Panel took 2.723630905151367s
Availability | SPARQL endpoint availability check for ProductDB took 0.7441637516021729s
Availability | VoID file availability check for ProductDB took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for ProductDB took 0.31505632400512695s
Reputation | Calculation of the PageRank for ProductDB took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.653236389160156e-05s
Believability | Calculation of trust value for ProductDB took 1.0967254638671875e-05s
INFO | --- Analysis for productdb took 4.12885594367981s
Availability | SPARQL endpoint availability check for Product Types Ontology took 9.489059448242188e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.318666934967041s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02105569839477539s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.677078247070312e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for productontology took 3.5564913749694824s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.5299530029296875e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.30496692657470703s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010752677917480469s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 6.985976219177246s
Availability | SPARQL endpoint availability check for provenanceweb took 0.0649411678314209s
Availability | VoID file availability check for provenanceweb took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.29846644401550293s
Reputation | Calculation of the PageRank for provenanceweb took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.128715515136719e-05s
Believability | Calculation of trust value for provenanceweb took 1.3828277587890625e-05s
INFO | --- Analysis for provenanceweb took 53.31792497634888s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 8.940696716308594e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2908594608306885s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.965896606445312e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.1205673217773438e-05s
INFO | --- Analysis for proyectoapadrina took 6.935288429260254s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.253326892852783s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008842945098876953s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.3187737464904785s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02160787582397461s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 4.1484832763671875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 9.298324584960938e-06s
INFO | --- Analysis for pscs-catalogue took 124.56304955482483s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.410743713378906e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2838869094848633s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.021982669830322266s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.843971252441406e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.33514404296875e-05s
INFO | --- Analysis for psh-subject-headings took 8.167700290679932s
Availability | SPARQL endpoint availability check for Depression took 0.8807754516601562s
Availability | VoID file availability check for Depression took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for Depression took 0.31008291244506836s
Reputation | Calculation of the PageRank for Depression took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for Depression took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Depression took 2.956390380859375e-05s
Believability | Calculation of trust value for Depression took 1.3589859008789062e-05s
INFO | --- Analysis for Psychology took 3.6730117797851562s
Availability | SPARQL endpoint availability check for PubChem RDF took 8.845329284667969e-05s
Availability | VoID file availability check for PubChem RDF took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.2763843536376953s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.3392181396484375e-05s
Believability | Calculation of trust value for PubChem RDF took 1.1205673217773438e-05s
INFO | --- Analysis for PubChem_RDF took 5.603135824203491s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.06541466712952s
Availability | VoID file availability check for Public Spending in Greece took 0.0007681846618652344s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.3003208637237549s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.153915405273438e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.4066696166992188e-05s
INFO | --- Analysis for public-spending-in-greece took 147.71510934829712s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.19086790084838867s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006437301635742188s
Extra | Recovery of all triples for Publications Office Authority tables took 167.91493606567383s
Performance | Total latancy measurement for Publications Office Authority tables took 0.6653754711151123s
Amount of data | Number of triples check for Publications Office Authority tables took 43.002862215042114s
Interoperability | New terms check for Publications Office Authority tables took 58.98108386993408s
Versatility | Languages check for Publications Office Authority tables took 300.1413240432739s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 15.210593938827515s
Security | Check HTTPS for Publications Office Authority tables took 0.36939287185668945s
Interpretability | RDF structures check for Publications Office Authority tables took 0.26849985122680664s
Versatility | Serialization formats check for Publications Office Authority tables took 3.3224806785583496s
Availability | RDF dump link check for Publications Office Authority tables took 0.23698687553405762s
License | MR license check for Publications Office Authority tables took 0.3506345748901367s
License | HR license check for Publications Office Authority tables took 300.05783772468567s
Amount of data | Number of property check for Publications Office Authority tables took 0.23973679542541504s
Understandability | Number of label check for Publications Office Authority tables took 1.568084478378296s
Understandability | URI regex check for Publications Office Authority tables took 0.409496545791626s
Understandability | Vocabs check for Publications Office Authority tables took 0.10893702507019043s
Verifiability | Authors check for Publications Office Authority tables took 0.1636357307434082s
Verifiability | Publishers check for Publications Office Authority tables took 0.20205950736999512s
Performance | Throughput check for Publications Office Authority tables took 10.701077461242676s
Amount of data | Check the number of entities for Publications Office Authority tables took 0.00010967254638671875s
Verifiability | Contribs. check for Publications Office Authority tables took 0.18197894096374512s
Interlinking | sameAs chians check for Publications Office Authority tables took 6.363767862319946s
Interlinking | skos check for Publications Office Authority tables took 0.17248821258544922s
Interlinking | skos check for Publications Office Authority tables took 0.14214420318603516s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.2609682083129883s
Currency | Creation date check for Publications Office Authority tables took 0.557152509689331s
Currency | Modification date check for Publications Office Authority tables took 0.16370558738708496s
Rep.Conc. | URIs length for Publications Office Authority tables took 415.06356930732727s
Interoperability | New vocabularies check for Publications Office Authority tables took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.16505837440490723s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.19428348541259766s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.15602350234985352s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 37.31926417350769s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.2040350437164307s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.6689329147338867s
Consistency | Disjoint class check for Publications Office Authority tables took 0.19678640365600586s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.3978636264801s
Consistency | Misplaced classes for Publications Office Authority tables took 8.442391872406006s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 71.19989347457886s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.771158218383789s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.4512755870819s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.1534929275512695s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.42877888679504395s
Security | Sign check for Publications Office Authority tables took 0.4304845333099365s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 11.427042007446289s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.8327767848968506s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.021434307098388672s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.6689300537109375e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 1.0013580322265625e-05s
INFO | --- Analysis for publications_office_authority_tables took 14851.853381156921s
Availability | SPARQL endpoint availability check for QBOAirbase took 8.559226989746094e-05s
Availability | VoID file availability check for QBOAirbase took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.29785656929016113s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020969867706298828s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.367134094238281e-05s
Believability | Calculation of trust value for QBOAirbase took 1.4543533325195312e-05s
INFO | --- Analysis for qboairbase took 22.585801362991333s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.410743713378906e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.29657530784606934s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.03231167793273926s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.743171691894531e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.2636184692382812e-05s
INFO | --- Analysis for Qualité_de_l'air took 3.1102957725524902s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 8.916854858398438e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.29532289505004883s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.021996021270751953s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.266334533691406e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.0967254638671875e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 47.20273280143738s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.6540427207946777s
Availability | VoID file availability check for Querolus in LiLa took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.30469393730163574s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for Querolus took 4.284276962280273s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3228905200958252s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007100105285644531s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 28.57348942756653s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7296240329742432s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.5064728260040283s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.941133975982666s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.670350313186646s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.6533031463623047s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.18188238143920898s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1321871280670166s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14266467094421387s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13237237930297852s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14270234107971191s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15480947494506836s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14371585845947266s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2817099094390869s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14231085777282715s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14265155792236328s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14167308807373047s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.657138109207153s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.033348083496094e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1421496868133545s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15305757522583008s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15266752243041992s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14273571968078613s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14284610748291016s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.28130435943603516s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3036336898803711s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 20.739295482635498s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14193964004516602s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.141066312789917s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13151025772094727s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14443039894104004s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.814697265625e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.084124803543091s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14660263061523438s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.847592115402222s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.800988674163818s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.3700952529907227s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.832083225250244s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.920989751815796s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14076995849609375s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.647854804992676s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.29293060302734375s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.430511474609375e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.4781951904296875e-05s
INFO | --- Analysis for racai-legalnero took 160.1650426387787s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 8.940696716308594e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.325516939163208s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.7894973754882812e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.1205673217773438e-05s
INFO | --- Analysis for racai-llod-corola-we took 2.9734485149383545s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.14325213432312012s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005929470062255859s
Extra | Recovery of all triples for PARSEME-Ro corpus took 30.227750539779663s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.7096593379974365s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.973002910614014s
Interoperability | New terms check for PARSEME-Ro corpus took 2.1992037296295166s
Versatility | Languages check for PARSEME-Ro corpus took 18.108502864837646s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.573613882064819s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.1439061164855957s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.14325976371765137s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.1535201072692871s
License | MR license check for PARSEME-Ro corpus took 0.14235377311706543s
License | HR license check for PARSEME-Ro corpus took 10.141996622085571s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.13082432746887207s
Understandability | Number of label check for PARSEME-Ro corpus took 0.1920452117919922s
Understandability | URI regex check for PARSEME-Ro corpus took 0.2828245162963867s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.14133048057556152s
Verifiability | Authors check for PARSEME-Ro corpus took 0.14320039749145508s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.15378189086914062s
Performance | Throughput check for PARSEME-Ro corpus took 11.10268521308899s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 7.510185241699219e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.14153289794921875s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.13056659698486328s
Interlinking | skos check for PARSEME-Ro corpus took 0.15254473686218262s
Interlinking | skos check for PARSEME-Ro corpus took 0.13016247749328613s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.13117480278015137s
Currency | Creation date check for PARSEME-Ro corpus took 0.28434014320373535s
Currency | Modification date check for PARSEME-Ro corpus took 0.26226806640625s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 79.60771059989929s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.14315414428710938s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.1399984359741211s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.13970303535461426s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 2.0175483226776123s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.22918391227722168s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 3.9511325359344482s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.13477849960327148s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.355522632598877s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 32.053640842437744s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.6030547618865967s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.007737636566162s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.9023704528808594s
Security | Sign check for PARSEME-Ro corpus took 0.13972783088684082s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.337401628494263s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.5032765865325928s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020087480545043945s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 4.291534423828125e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.2874603271484375e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 281.4844355583191s
Availability | SPARQL endpoint availability check for RoLEX took 0.14111685752868652s
Availability | VoID file availability check for RoLEX took 0.0005428791046142578s
Extra | Recovery of all triples for RoLEX took 34.408071756362915s
Performance | Total latancy measurement for RoLEX took 0.7410705089569092s
Amount of data | Number of triples check for RoLEX took 1.655580997467041s
Interoperability | New terms check for RoLEX took 1.7247965335845947s
Versatility | Languages check for RoLEX took 4.148063898086548s
Interpretability | Number of blank nodes check for RoLEX took 1.0780372619628906s
Interpretability | RDF structures check for RoLEX took 0.14601659774780273s
Versatility | Serialization formats check for RoLEX took 0.15450215339660645s
Availability | RDF dump link check for RoLEX took 0.13034510612487793s
License | MR license check for RoLEX took 0.15489625930786133s
License | HR license check for RoLEX took 0.15385794639587402s
Amount of data | Number of property check for RoLEX took 0.14131379127502441s
Understandability | Number of label check for RoLEX took 0.14326691627502441s
Understandability | URI regex check for RoLEX took 0.2851285934448242s
Understandability | Vocabs check for RoLEX took 0.1317291259765625s
Verifiability | Authors check for RoLEX took 0.14165449142456055s
Verifiability | Publishers check for RoLEX took 0.1426548957824707s
Performance | Throughput check for RoLEX took 10.735458850860596s
Amount of data | Check the number of entities for RoLEX took 6.985664367675781e-05s
Verifiability | Contribs. check for RoLEX took 0.1424112319946289s
Interlinking | sameAs chians check for RoLEX took 0.14215588569641113s
Interlinking | skos check for RoLEX took 0.14021706581115723s
Interlinking | skos check for RoLEX took 0.13126754760742188s
Timeliness | dataset update frequency check for RoLEX took 0.14200973510742188s
Currency | Creation date check for RoLEX took 0.2860872745513916s
Currency | Modification date check for RoLEX took 0.28348422050476074s
Rep.Conc. | URIs length for RoLEX took 55.922887086868286s
Interoperability | New vocabularies check for RoLEX took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.14101529121398926s
Accuracy | Check Functional Property for RoLEX took 0.1414024829864502s
Accuracy | Check Inverse Functional Property for RoLEX took 0.14156484603881836s
Accuracy | Check Datatype consistency for RoLEX took 4.043052911758423s
Consistency | Disjoint class check for RoLEX took 0.1422879695892334s
Consistency | Check Misplaced properties for RoLEX took 2.674755334854126s
Consistency | Check Ontology hijacking for RoLEX took 8.557910442352295s
Consistency | Check Invalid usage of undefined classes for RoLEX took 1.9144766330718994s
Consistency | Check Invalid usage of undefined properties for RoLEX took 4.0322935581207275s
Conciseness | Check Extensional conciseness for RoLEX took 3.177260398864746s
Security | Sign check for RoLEX took 0.15226984024047852s
Availability | Check URIs Dereferenciability for RoLEX took 7.267225980758667s
Completeness | Calculation of interlinking completeness for RoLEX took 0.4078660011291504s
Reputation | Calculation of the PageRank for RoLEX took 0.02083301544189453s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.075599670410156e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 2.384185791015625e-06s
Believability | Calculation of trust value for RoLEX took 1.4066696166992188e-05s
INFO | --- Analysis for racai-llod-rolex took 174.30189037322998s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2720766067504883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.0040740966796875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.3909759521484375e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.9574334621429443s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 8.702278137207031e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.3010590076446533s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.021918058395385742s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.7418136596679688e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.430511474609375e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.920201539993286s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 8.988380432128906e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.27761006355285645s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.02122974395751953s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.4332275390625e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.826470136642456s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 7.510185241699219e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.30722737312316895s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.021352529525756836s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.314018249511719e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.430511474609375e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.953744888305664s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.134141206741333s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0009527206420898438s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.384081363677979s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.7165052890777588s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.3119826316833496s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.4426004886627197s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.5818228721618652s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.26920318603515625s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.14037656784057617s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.14116621017456055s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.15037989616394043s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.14106297492980957s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.1368086338043213s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.1499779224395752s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.1352531909942627s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.27948880195617676s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.12958264350891113s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.14139699935913086s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.1404402256011963s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.778947353363037s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 6.532669067382812e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.15106558799743652s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.13996148109436035s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14063572883605957s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.13997554779052734s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.13029050827026367s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.2573883533477783s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.25931644439697266s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.5066144466400146s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.14017033576965332s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.150254487991333s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.1304326057434082s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.382366418838501s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009750127792358398s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.1925334930419922s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.14077377319335938s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5082600116729736s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.1187219619750977s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.2664766311645508s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.6348240375518799s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8545007705688477s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.12711358070373535s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 3613.833167552948s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.7967474460601807s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.02155923843383789s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 6.341934204101562e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 2.1457672119140625e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.0967254638671875e-05s
INFO | --- Analysis for racai-llod-rtasc took 3671.7158262729645s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.14165973663330078s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005471706390380859s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 34.01023554801941s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.7073893547058105s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0841865539550781s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.4826219081878662s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.4342775344848633s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8594248294830322s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.14395475387573242s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.14208722114562988s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.14008212089538574s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.12936735153198242s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.6013007164001465s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.1306900978088379s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.16063570976257324s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.2949185371398926s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.1528480052947998s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.13219642639160156s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.13113760948181152s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.86871337890625s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 7.081031799316406e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.1426246166229248s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.1525578498840332s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.1538233757019043s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15433192253112793s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.1541275978088379s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.2859609127044678s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.26317358016967773s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.260600566864014s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.12896251678466797s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.13882017135620117s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.13156366348266602s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.7189915180206299s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.018668413162231445s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 3.971859931945801s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.15488004684448242s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.6959128379821777s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.581461191177368s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.3210878372192383s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.8674938678741455s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 3.033501625061035s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.14188194274902344s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1528.1572897434235s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.45085978507995605s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.02149653434753418s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.9073486328125e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-simonero took 1631.740981578827s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.13123536109924316s
Availability | VoID file availability check for Rådata nå! took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2906155586242676s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Rådata nå! took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.058547973632812e-05s
Believability | Calculation of trust value for Rådata nå! took 1.33514404296875e-05s
INFO | --- Analysis for radatana took 4.472355604171753s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.893013000488281e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.32550549507141113s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.0223233699798584s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.719329833984375e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.1444091796875e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.199530124664307s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.998428583145142s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2977256774902344s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02367687225341797s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.314018249511719e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.2636184692382812e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 28.969884872436523s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 391.95308351516724s
Availability | VoID file availability check for Polish LGU financial statements took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.34685325622558594s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.147125244140625e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.2159347534179688e-05s
INFO | --- Analysis for Rb_PL_LGU took 666.9711277484894s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.363059997558594e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2978668212890625s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.606910705566406e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.3113021850585938e-05s
INFO | --- Analysis for rdf-book-mashup took 3.8113958835601807s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 0.00010895729064941406s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.29370927810668945s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.02189493179321289s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010132789611816406s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.33514404296875e-05s
INFO | --- Analysis for rdfize-lastfm took 2.8101232051849365s
Availability | SPARQL endpoint availability check for RDFLicense took 260.63000106811523s
Availability | VoID file availability check for RDFLicense took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.3352010250091553s
Reputation | Calculation of the PageRank for RDFLicense took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for RDFLicense took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.62396240234375e-05s
Believability | Calculation of trust value for RDFLicense took 1.1444091796875e-05s
INFO | --- Analysis for rdflicense took 535.6724717617035s
Availability | SPARQL endpoint availability check for RDFohloh took 4.410743713378906e-05s
Availability | VoID file availability check for RDFohloh took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.29109692573547363s
Reputation | Calculation of the PageRank for RDFohloh took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for RDFohloh took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 8.940696716308594e-05s
Believability | Calculation of trust value for RDFohloh took 1.2874603271484375e-05s
INFO | --- Analysis for rdfohloh took 8.331534385681152s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6686134338378906s
Availability | VoID file availability check for Reactome RDF took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.3053276538848877s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for Reactome RDF took 1.2636184692382812e-05s
INFO | --- Analysis for reactome-rdf took 4.097735166549683s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.10875153541564941s
Availability | VoID file availability check for Rechtspraak.nl took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.2985668182373047s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.022360563278198242s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.894371032714844e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 9.775161743164062e-06s
INFO | --- Analysis for rechtspraak took 2.8722984790802s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.291534423828125e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.3006904125213623s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 0.00010418891906738281s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.1444091796875e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 6.666119575500488s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.09206318855285645s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.3721919059753418s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.02252960205078125s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015425682067871094s
Believability | Calculation of trust value for reference.data.gov.uk took 8.821487426757812e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.872344493865967s
Availability | SPARQL endpoint availability check for RELD took 0.6085712909698486s
Availability | VoID file availability check for RELD took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for RELD took 0.29709529876708984s
Reputation | Calculation of the PageRank for RELD took 0.022113561630249023s
Interlinking | Calculation of Degree of Connection for RELD took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RELD took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for RELD took 2.956390380859375e-05s
Believability | Calculation of trust value for RELD took 1.2159347534179688e-05s
INFO | --- Analysis for RELD took 4.120067596435547s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.20839548110961914s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005657672882080078s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 0.9564089775085449s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.4311361312866211s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.2626092433929443s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.5867316722869873s
Versatility | Languages check for Repository for Linked Open Archival Data took 19.284179210662842s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 26.74286437034607s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.22416114807128906s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.2048168182373047s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.23337340354919434s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.16892123222351074s
License | MR license check for Repository for Linked Open Archival Data took 0.27433156967163086s
License | HR license check for Repository for Linked Open Archival Data took 7.923619270324707s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.14986634254455566s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.8873434066772461s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.39446067810058594s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.1024625301361084s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.14631080627441406s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.16043949127197266s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.673982858657837s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.00011134147644042969s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.08151078224182129s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.11432909965515137s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.23044276237487793s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.06800484657287598s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.20719218254089355s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.1956634521484375s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.17519211769104004s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.5787434577941895s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.10288286209106445s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.09791707992553711s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.061008453369140625s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.3634755611419678s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.028269529342651367s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.0284879207611084s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.17789101600646973s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.9055590629577637s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.1770176887512207s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.572713851928711s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.2503156661987305s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.034928321838379s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.03417706489562988s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.1416623592376709s
Security | Sign check for Repository for Linked Open Archival Data took 0.400113582611084s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1028.4674305915833s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.7718567848205566s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02332305908203125s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 7.081031799316406e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0008697509765625s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.4066696166992188e-05s
INFO | --- Analysis for reload took 1178.5253863334656s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.410743713378906e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.2926499843597412s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.022848844528198242s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0009310245513916016s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.600120544433594e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.2636184692382812e-05s
INFO | --- Analysis for remote_Sensing took 3.5058016777038574s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.712944746017456s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.29723548889160156s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020975589752197266s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.601478576660156e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 7.62939453125e-06s
INFO | --- Analysis for renewable_energy_generators took 11.532477140426636s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.06311917304992676s
Availability | VoID file availability check for research.data.gov.uk took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.3574540615081787s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.179115295410156e-05s
Believability | Calculation of trust value for research.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for research-data-gov-uk took 2.8599376678466797s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 9.393692016601562e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.3107597827911377s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.02180647850036621s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 7.104873657226562e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.33514404296875e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.572576999664307s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.0639493465423584s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.31339144706726074s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020863056182861328s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.147125244140625e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.2636184692382812e-05s
INFO | --- Analysis for revistas_turismo took 2.839308023452759s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.29077696800231934s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2867405414581299s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011587142944335938s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.33514404296875e-05s
INFO | --- Analysis for revyu took 2.950805902481079s
Availability | SPARQL endpoint availability check for sdafsadf took 0.36062073707580566s
Availability | VoID file availability check for sdafsadf took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.27716660499572754s
Reputation | Calculation of the PageRank for sdafsadf took 0.020915746688842773s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.719329833984375e-05s
Believability | Calculation of trust value for sdafsadf took 1.2159347534179688e-05s
INFO | --- Analysis for rgsdfg took 3.5637097358703613s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 8.630752563476562e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.28173303604125977s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.601478576660156e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.239776611328125e-05s
INFO | --- Analysis for riese took 22.95146346092224s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.32064294815063477s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006830692291259766s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 25.93139934539795s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.4808659553527832s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 50.58025527000427s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 2.108921527862549s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 145.93548822402954s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 46.959233045578s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.24092721939086914s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.16454434394836426s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.15649628639221191s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.0985865592956543s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.14171814918518066s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.0990996360779s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.1493053436279297s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 9.565504789352417s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.2457108497619629s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.10927963256835938s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.0843961238861084s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.09187602996826172s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.364498138427734s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 8.082389831542969e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.1021578311920166s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.3819198608398438s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.15275263786315918s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.1020205020904541s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.09110713005065918s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.2474372386932373s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.21676993370056152s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 74.46997833251953s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.13020586967468262s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.12719130516052246s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.09561038017272949s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 17.732081413269043s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.3943898677825928s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.7337894439697266s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.09707069396972656s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 48.00580954551697s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 4.754573583602905s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.286515712738037s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 47.403414249420166s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.836479425430298s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.10543060302734375s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1014.0363001823425s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.5199873447418213s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 1.6689300537109375e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.1205673217773438e-05s
INFO | --- Analysis for rism took 1936.9235241413116s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.09105706214904785s
Availability | VoID file availability check for RISM Authority data took 0.0005636215209960938s
Extra | Recovery of all triples for RISM Authority data took 21.739847660064697s
Performance | Total latancy measurement for RISM Authority data took 0.4822356700897217s
Amount of data | Number of triples check for RISM Authority data took 52.46887731552124s
Interoperability | New terms check for RISM Authority data took 1.5681970119476318s
Versatility | Languages check for RISM Authority data took 155.37370777130127s
Interpretability | Number of blank nodes check for RISM Authority data took 49.93939280509949s
Security | Check HTTPS for RISM Authority data took 0.247908353805542s
Interpretability | RDF structures check for RISM Authority data took 0.15126395225524902s
Versatility | Serialization formats check for RISM Authority data took 0.11748552322387695s
Availability | RDF dump link check for RISM Authority data took 0.09531521797180176s
License | MR license check for RISM Authority data took 0.1461944580078125s
License | HR license check for RISM Authority data took 300.09714937210083s
Amount of data | Number of property check for RISM Authority data took 0.1319882869720459s
Understandability | Number of label check for RISM Authority data took 5.93264365196228s
Understandability | URI regex check for RISM Authority data took 0.2358551025390625s
Understandability | Vocabs check for RISM Authority data took 0.0838003158569336s
Verifiability | Authors check for RISM Authority data took 0.09541630744934082s
Verifiability | Publishers check for RISM Authority data took 0.08457183837890625s
Performance | Throughput check for RISM Authority data took 10.529355525970459s
Amount of data | Check the number of entities for RISM Authority data took 0.00011086463928222656s
Verifiability | Contribs. check for RISM Authority data took 0.11735343933105469s
Interlinking | sameAs chians check for RISM Authority data took 1.2681386470794678s
Interlinking | skos check for RISM Authority data took 0.1392209529876709s
Interlinking | skos check for RISM Authority data took 0.10582184791564941s
Timeliness | dataset update frequency check for RISM Authority data took 0.11439132690429688s
Currency | Creation date check for RISM Authority data took 0.26013827323913574s
Currency | Modification date check for RISM Authority data took 0.22609949111938477s
Rep.Conc. | URIs length for RISM Authority data took 77.70259165763855s
Interoperability | New vocabularies check for RISM Authority data took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.15168547630310059s
Accuracy | Check Functional Property for RISM Authority data took 0.1236271858215332s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.10683846473693848s
Accuracy | Check Empty annotation labels for RISM Authority data took 11.25115418434143s
Accuracy | Check White space in annotation for RISM Authority data took 2.397927761077881s
Accuracy | Check Datatype consistency for RISM Authority data took 3.820249557495117s
Consistency | Disjoint class check for RISM Authority data took 0.10860109329223633s
Consistency | Check Misplaced properties for RISM Authority data took 45.820377349853516s
Consistency | Check Ontology hijacking for RISM Authority data took 4.90336537361145s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.3771893978118896s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 48.9368212223053s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.97770357131958s
Security | Sign check for RISM Authority data took 0.1033942699432373s
Availability | Check URIs Dereferenciability for RISM Authority data took 1047.9794194698334s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.7448244094848633s
Reputation | Calculation of the PageRank for RISM Authority data took 0.021104097366333008s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 2.1457672119140625e-06s
Believability | Calculation of trust value for RISM Authority data took 1.0728836059570312e-05s
INFO | --- Analysis for rism-authorities took 1978.1912426948547s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.458427429199219e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.28855109214782715s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.022266864776611328s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for engineering equipment ontology took 9.775161743164062e-06s
INFO | --- Analysis for rk took 2.650386095046997s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.03691983222961426s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.28820371627807617s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.022806167602539062s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002231597900390625s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-acm took 2.7597320079803467s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.04379916191101074s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.31899118423461914s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02127838134765625s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013875961303710938s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.748957633972168s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.04399847984313965s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.31154513359069824s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020816326141357422s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00020003318786621094s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.846771478652954s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.04249429702758789s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2794761657714844s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.022459983825683594s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00016307830810546875s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-cordis took 2.801114797592163s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.058843374252319336s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.2853085994720459s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0001590251922607422s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.856154203414917s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.04794621467590332s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2964975833892822s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.022100210189819336s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.886222839355469e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.8335623741149902s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.04600167274475098s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.28577303886413574s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.022388935089111328s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00012946128845214844s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.736816644668579s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04279041290283203s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.32109689712524414s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02106022834777832s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.793571472167969e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.8306777477264404s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04143929481506348s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.3204379081726074s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02169942855834961s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002353191375732422s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.830782413482666s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04839277267456055s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.31442713737487793s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02285170555114746s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.534027099609375e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 2.8999900817871094s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.38937854766845703s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.3019144535064697s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02086663246154785s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.5367431640625e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-deploy took 4.0530314445495605s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.035657644271850586s
Availability | VoID file availability check for digitaleconomy took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.2992405891418457s
Reputation | Calculation of the PageRank for digitaleconomy took 0.021877288818359375s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.0279159545898438e-05s
Believability | Calculation of trust value for digitaleconomy took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.749375820159912s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.0452115535736084s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2915456295013428s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014448165893554688s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.9241783618927s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.045774221420288086s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.4753873348236084s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02181529998779297s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.792213439941406e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-ecs took 3.6571857929229736s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.04560112953186035s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.27165865898132324s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.022433042526245117s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001780986785888672s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.818019151687622s
Availability | SPARQL endpoint availability check for epsrc took 0.05136680603027344s
Availability | VoID file availability check for epsrc took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for epsrc took 0.29570674896240234s
Reputation | Calculation of the PageRank for epsrc took 0.02171921730041504s
Interlinking | Calculation of Degree of Connection for epsrc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.8650970458984375e-05s
Believability | Calculation of trust value for epsrc took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.796018123626709s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.035248517990112305s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00042724609375s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.393876314163208s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.02148604393005371s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.511543273925781e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-era took 2.8923354148864746s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.042443275451660156s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.3028872013092041s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010347366333007812s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.8275952339172363s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.41615748405456543s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.3005406856536865s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.02120828628540039s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.7738037109375e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-ft took 4.38624906539917s
Availability | SPARQL endpoint availability check for fun took 0.04648613929748535s
Availability | VoID file availability check for fun took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for fun took 0.28685665130615234s
Reputation | Calculation of the PageRank for fun took 0.021364450454711914s
Interlinking | Calculation of Degree of Connection for fun took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for fun took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for fun took 7.462501525878906e-05s
Believability | Calculation of trust value for fun took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.7319939136505127s
Availability | SPARQL endpoint availability check for gdlc took 0.05229377746582031s
Availability | VoID file availability check for gdlc took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for gdlc took 0.29723024368286133s
Reputation | Calculation of the PageRank for gdlc took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for gdlc took 7.128715515136719e-05s
Believability | Calculation of trust value for gdlc took 4.839897155761719e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.82401180267334s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.03437328338623047s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.3445301055908203s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011420249938964844s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.8338053226470947s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.04710221290588379s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.29131507873535156s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.02125835418701172s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001361370086669922s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.897966146469116s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.04267168045043945s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.29810380935668945s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02068185806274414s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001385211944580078s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.9187140464782715s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.051493167877197266s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2984428405761719s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02174687385559082s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.198883056640625e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.7819831371307373s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.03580594062805176s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2926042079925537s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.021383047103881836s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.677078247070312e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.843681573867798s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.04277229309082031s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.3143885135650635s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.022645950317382812s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.410743713378906e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.8195629119873047s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.046140193939208984s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.3273653984069824s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001614093780517578s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.7895169258117676s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.05150413513183594s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.30507659912109375s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.021195650100708008s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00015163421630859375s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-laas took 2.7805545330047607s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04141092300415039s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.29583096504211426s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02080225944519043s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.437301635742188e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.6981141567230225s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.03548789024353027s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.27504992485046387s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015616416931152344s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.7756597995758057s
Availability | SPARQL endpoint availability check for notube took 0.046251535415649414s
Availability | VoID file availability check for notube took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for notube took 0.27908968925476074s
Reputation | Calculation of the PageRank for notube took 0.02174091339111328s
Interlinking | Calculation of Degree of Connection for notube took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for notube took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for notube took 4.744529724121094e-05s
Believability | Calculation of trust value for notube took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.7262473106384277s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.04950118064880371s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.3189084529876709s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.000133514404296875s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.7243542671203613s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.04752349853515625s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2765042781829834s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020897388458251953s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015783309936523438s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-oai took 2.6593687534332275s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.05499529838562012s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.264845609664917s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.653236389160156e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-os took 2.7981786727905273s
Availability | SPARQL endpoint availability check for photos took 0.05011391639709473s
Availability | VoID file availability check for photos took 0.0004200935363769531s
Completeness | Calculation of interlinking completeness for photos took 0.27364587783813477s
Reputation | Calculation of the PageRank for photos took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for photos took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for photos took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for photos took 7.104873657226562e-05s
Believability | Calculation of trust value for photos took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-photos took 2.7062816619873047s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04578542709350586s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.30208730697631836s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.024416208267211914s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011396408081054688s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-pisa took 2.8623976707458496s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0458681583404541s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.29175639152526855s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.021860599517822266s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019788742065429688s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.7959353923797607s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.043837785720825195s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.3469107151031494s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.021369218826293945s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00014472007751464844s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-resex took 2.9489047527313232s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.042079925537109375s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.2974588871002197s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.202957153320312e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.8716042041778564s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.05169034004211426s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2780129909515381s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0001251697540283203s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-roma took 2.922297716140747s
Availability | SPARQL endpoint availability check for roni took 0.06154441833496094s
Availability | VoID file availability check for roni took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for roni took 0.28315138816833496s
Reputation | Calculation of the PageRank for roni took 0.02359747886657715s
Interlinking | Calculation of Degree of Connection for roni took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for roni took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for roni took 3.170967102050781e-05s
Believability | Calculation of trust value for roni took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-roni took 2.6912786960601807s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.05271029472351074s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.3258490562438965s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.021221637725830078s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00023245811462402344s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.815798759460449s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.0487973690032959s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.31848692893981934s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.021178722381591797s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.001049041748046875s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00013780593872070312s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.8490118980407715s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.04291939735412598s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.31853222846984863s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02097320556640625s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010037422180175781s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.8296518325805664s
Availability | SPARQL endpoint availability check for webconf took 0.050640106201171875s
Availability | VoID file availability check for webconf took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for webconf took 0.3080768585205078s
Reputation | Calculation of the PageRank for webconf took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for webconf took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for webconf took 0.000110626220703125s
Believability | Calculation of trust value for webconf took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-webconf took 13.372216939926147s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.043447017669677734s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.28420495986938477s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02178049087524414s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.033348083496094e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.8204874992370605s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04482007026672363s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.3519265651702881s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.022205591201782227s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.000209808349609375s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.8311543464660645s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.04619288444519043s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.33187413215637207s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.021428585052490234s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.703636169433594e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 2.7358365058898926s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.2586538791656494s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0007040500640869141s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 39.6023051738739s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.45358729362487793s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.4276049137115479s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.5688955783843994s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.299605369567871s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.2307443618774414s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.09641718864440918s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.0893089771270752s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.09321355819702148s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.0940544605255127s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.08008933067321777s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.10715699195861816s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.08824920654296875s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.1570584774017334s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.07894086837768555s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.09429931640625s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.07927608489990234s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.472420454025269s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 6.985664367675781e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.08084297180175781s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.08084511756896973s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.095947265625s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.09592342376708984s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.08915257453918457s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.17531585693359375s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.2273240089416504s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 18.47572946548462s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.0955972671508789s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08498144149780273s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.07790780067443848s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.803781270980835s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.09387969970703125s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 2.7779269218444824s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 6.817716360092163s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.4439952373504639s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.085555791854858s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.1792690753936768s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.07680821418762207s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 496.2585914134979s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.4283285140991211s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.021305084228515625s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.630752563476562e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.86102294921875e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 9.5367431640625e-06s
INFO | --- Analysis for roceeh-road took 616.8045599460602s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.76837158203125e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.2870781421661377s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.0279159545898438e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.2159347534179688e-05s
INFO | --- Analysis for ROSHANI took 4.801448583602905s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 6.818771362304688e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.26908183097839355s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.4332275390625e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 8.106231689453125e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.71932315826416s
Availability | SPARQL endpoint availability check for x took 9.250640869140625e-05s
Availability | VoID file availability check for x took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for x took 0.27681422233581543s
Reputation | Calculation of the PageRank for x took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for x took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for x took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for x took 3.1948089599609375e-05s
Believability | Calculation of trust value for x took 7.62939453125e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.632678508758545s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 8.988380432128906e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.28888368606567383s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.794929504394531e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.867813110351562e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 4.75449013710022s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 8.463859558105469e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.00039839744567871094s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.31098413467407227s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020794153213500977s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.000997781753540039s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 9.012222290039062e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 7.867813110351562e-06s
INFO | --- Analysis for rubentaelman took 3.300208568572998s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 5.221366882324219e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2712137699127197s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020815134048461914s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.559226989746094e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 8.821487426757812e-06s
INFO | --- Analysis for rubenverborgh took 3.358942747116089s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.2746512889862s
Availability | VoID file availability check for Russian Universities Specialities took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.29418301582336426s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.021274805068969727s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.3392181396484375e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.33514404296875e-05s
INFO | --- Analysis for russian-universities-specialities took 675.5014336109161s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.3812179565429688s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.32041215896606445s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.021783113479614258s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.457069396972656e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.3828277587890625e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 8.248339414596558s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.0257623195648193s
Availability | VoID file availability check for SALDO-RDF took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2807044982910156s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02098250389099121s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for SALDO-RDF took 5.245208740234375e-06s
INFO | --- Analysis for saldo-rdf took 5.910617113113403s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6544911861419678s
Availability | VoID file availability check for SALDOM-RDF took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2702205181121826s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.021425962448120117s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.0728836059570312e-05s
INFO | --- Analysis for saldom-rdf took 5.106689214706421s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 5.435943603515625e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.3170454502105713s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.021860599517822266s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010442733764648438s
Believability | Calculation of trust value for Salzburgerland DE took 1.0013580322265625e-05s
INFO | --- Analysis for salzburgerland-com-de took 3.4222748279571533s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 8.749961853027344e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.2857809066772461s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.0215146541595459s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.0001289844512939453s
Believability | Calculation of trust value for Salzburgerland EN took 1.2636184692382812e-05s
INFO | --- Analysis for salzburgerland-com-en took 3.2552802562713623s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.649162292480469e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.3005945682525635s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.02138042449951172s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010466575622558594s
Believability | Calculation of trust value for Salzburgerland IT took 1.2636184692382812e-05s
INFO | --- Analysis for salzburgerland-com-it took 3.1366567611694336s
Availability | SPARQL endpoint availability check for sandrart.net took 8.869171142578125e-05s
Availability | VoID file availability check for sandrart.net took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.26842689514160156s
Reputation | Calculation of the PageRank for sandrart.net took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.842613220214844e-05s
Believability | Calculation of trust value for sandrart.net took 1.0251998901367188e-05s
INFO | --- Analysis for sandrart-net took 3.965505599975586s
Availability | SPARQL endpoint availability check for Taxons  took 0.29575681686401367s
Availability | VoID file availability check for Taxons  took 0.0005452632904052734s
Extra | Recovery of all triples for Taxons  took 16.32270050048828s
Performance | Total latancy measurement for Taxons  took 0.44853878021240234s
Amount of data | Number of triples check for Taxons  took 2.233903169631958s
Interoperability | New terms check for Taxons  took 1.8556864261627197s
Versatility | Languages check for Taxons  took 38.348371267318726s
Interpretability | Number of blank nodes check for Taxons  took 0.9718132019042969s
Security | Check HTTPS for Taxons  took 0.1975235939025879s
Interpretability | RDF structures check for Taxons  took 0.8942170143127441s
Versatility | Serialization formats check for Taxons  took 0.42957353591918945s
Availability | RDF dump link check for Taxons  took 0.24107909202575684s
License | MR license check for Taxons  took 1.4183874130249023s
License | HR license check for Taxons  took 1.8554790019989014s
Amount of data | Number of property check for Taxons  took 0.12279486656188965s
Understandability | Number of label check for Taxons  took 2.3769752979278564s
Understandability | URI regex check for Taxons  took 0.6374459266662598s
Understandability | Vocabs check for Taxons  took 0.18124938011169434s
Verifiability | Authors check for Taxons  took 0.0942995548248291s
Verifiability | Publishers check for Taxons  took 0.08307218551635742s
Performance | Throughput check for Taxons  took 10.588914155960083s
Amount of data | Check the number of entities for Taxons  took 6.413459777832031e-05s
Verifiability | Contribs. check for Taxons  took 0.0962371826171875s
Interlinking | sameAs chians check for Taxons  took 0.14537882804870605s
Interlinking | skos check for Taxons  took 0.15267181396484375s
Interlinking | skos check for Taxons  took 0.09935164451599121s
Timeliness | dataset update frequency check for Taxons  took 0.37142062187194824s
Currency | Creation date check for Taxons  took 0.18681836128234863s
Currency | Modification date check for Taxons  took 0.21067571640014648s
Rep.Conc. | URIs length for Taxons  took 7.483462572097778s
Interoperability | New vocabularies check for Taxons  took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.11911392211914062s
Accuracy | Check Functional Property for Taxons  took 0.3199176788330078s
Accuracy | Check Inverse Functional Property for Taxons  took 0.2816932201385498s
Accuracy | Check Empty annotation labels for Taxons  took 3.8736329078674316s
Accuracy | Check White space in annotation for Taxons  took 0.3063623905181885s
Accuracy | Check Datatype consistency for Taxons  took 0.26457929611206055s
Consistency | Disjoint class check for Taxons  took 0.10770535469055176s
Consistency | Check Misplaced properties for Taxons  took 3.875359535217285s
Consistency | Misplaced classes for Taxons  took 0.9390935897827148s
Consistency | Check Ontology hijacking for Taxons  took 4.646263837814331s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.31496262550354s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.427703857421875s
Conciseness | Check Extensional conciseness for Taxons  took 0.29567694664001465s
Conciseness | Check Intensional conciseness for Taxons  took 0.18850374221801758s
Security | Sign check for Taxons  took 1.0288584232330322s
Availability | Check URIs Dereferenciability for Taxons  took 1755.8201775550842s
Completeness | Calculation of interlinking completeness for Taxons  took 0.5215244293212891s
Reputation | Calculation of the PageRank for Taxons  took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for Taxons  took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 6.67572021484375e-06s
Believability | Calculation of trust value for Taxons  took 1.1205673217773438e-05s
INFO | --- Analysis for sandre took 1934.71267080307s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.676133155822754s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.00041294097900390625s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.3259298801422119s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 2.956390380859375e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 7.62939453125e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 7.514547348022461s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 264.29676127433777s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.3682425022125244s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.02134847640991211s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.4066696166992188e-05s
INFO | --- Analysis for santillana_guide_dataset took 669.1757969856262s
Availability | SPARQL endpoint availability check for SATAR test  took 4.57763671875e-05s
Availability | VoID file availability check for SATAR test  took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.29123950004577637s
Reputation | Calculation of the PageRank for SATAR test  took 0.0220487117767334s
Interlinking | Calculation of Degree of Connection for SATAR test  took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.9087066650390625e-05s
Believability | Calculation of trust value for SATAR test  took 1.2874603271484375e-05s
INFO | --- Analysis for SATAR_test took 5.175757169723511s
Availability | SPARQL endpoint availability check for SCBG Data took 21.91531753540039s
Availability | VoID file availability check for SCBG Data took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.3036656379699707s
Reputation | Calculation of the PageRank for SCBG Data took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.20159912109375e-05s
Believability | Calculation of trust value for SCBG Data took 1.0967254638671875e-05s
INFO | --- Analysis for SCBG-Data took 54.7293438911438s
Availability | SPARQL endpoint availability check for Schemantra took 8.654594421386719e-05s
Availability | VoID file availability check for Schemantra took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Schemantra took 0.3156914710998535s
Reputation | Calculation of the PageRank for Schemantra took 0.02219223976135254s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Schemantra took 4.1484832763671875e-05s
Believability | Calculation of trust value for Schemantra took 1.1205673217773438e-05s
INFO | --- Analysis for Schemantra took 2.740628957748413s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 0.7725274562835693s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.3344132900238037s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.02224254608154297s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.457069396972656e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.0013580322265625e-05s
INFO | --- Analysis for schemapedia took 3.820732355117798s
Availability | SPARQL endpoint availability check for Scholarometer took 8.749961853027344e-05s
Availability | VoID file availability check for Scholarometer took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.3161931037902832s
Reputation | Calculation of the PageRank for Scholarometer took 0.026494503021240234s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 9.1552734375e-05s
Believability | Calculation of trust value for Scholarometer took 1.430511474609375e-05s
INFO | --- Analysis for scholarometer took 7.355775594711304s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 8.916854858398438e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2815060615539551s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.02168750762939453s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.0040740966796875e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 9.059906005859375e-06s
INFO | --- Analysis for scoreboard took 4.988097906112671s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.00011515617370605469s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.31194615364074707s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020902395248413086s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.504753112792969e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.2636184692382812e-05s
INFO | --- Analysis for SDDEC took 28.552329778671265s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.267692565917969e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.29003000259399414s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 2.9087066650390625e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0967254638671875e-05s
INFO | --- Analysis for SDG took 3.4458954334259033s
Availability | SPARQL endpoint availability check for sears.com took 9.012222290039062e-05s
Availability | VoID file availability check for sears.com took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for sears.com took 0.29311633110046387s
Reputation | Calculation of the PageRank for sears.com took 0.02094554901123047s
Interlinking | Calculation of Degree of Connection for sears.com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.67572021484375e-05s
Believability | Calculation of trust value for sears.com took 5.9604644775390625e-06s
INFO | --- Analysis for sears took 6.924354076385498s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.08713459968566895s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.27598094940185547s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.02080821990966797s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.416175842285156e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.298324584960938e-06s
INFO | --- Analysis for sec-rdfabout took 6.540198564529419s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.5210177898407s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.30808019638061523s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.021082401275634766s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 9.34600830078125e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for secold took 167.86434936523438s
Availability | SPARQL endpoint availability check for semanlink took 0.00010061264038085938s
Availability | VoID file availability check for semanlink took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for semanlink took 0.35939908027648926s
Reputation | Calculation of the PageRank for semanlink took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for semanlink took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014281272888183594s
Believability | Calculation of trust value for semanlink took 1.1920928955078125e-05s
INFO | --- Analysis for semanlink took 124.50028276443481s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.10184288024902344s
Availability | VoID file availability check for Semantic Universe Data took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.31189656257629395s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.021441936492919922s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Semantic Universe Data took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-universe took 2.8536977767944336s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.591208934783936s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0008020401000976562s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2893393039703369s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.021132707595825195s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011897087097167969s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.0728836059570312e-05s
INFO | --- Analysis for semantic-web-dog-food took 83.5693302154541s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 9.083747863769531e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.3131110668182373s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.3392181396484375e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.2435805797576904s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 8.821487426757812e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2920818328857422s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.02183842658996582s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.20159912109375e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 9.059906005859375e-06s
INFO | --- Analysis for semantic-xbrl took 3.7019197940826416s
Availability | SPARQL endpoint availability check for Semantic Quran took 5.038911819458008s
Availability | VoID file availability check for Semantic Quran took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.3070077896118164s
Reputation | Calculation of the PageRank for Semantic Quran took 0.021691560745239258s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Semantic Quran took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 7.033348083496094e-05s
Believability | Calculation of trust value for Semantic Quran took 1.1920928955078125e-05s
INFO | --- Analysis for semanticquran took 14.900532960891724s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.506111145019531e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.3298933506011963s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02114272117614746s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.8650970458984375e-05s
Believability | Calculation of trust value for SemanticTweet took 1.1920928955078125e-05s
INFO | --- Analysis for semantictweet took 2.7934083938598633s
Availability | SPARQL endpoint availability check for semanticweb.org took 8.678436279296875e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.33640313148498535s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.62939453125e-05s
Believability | Calculation of trust value for semanticweb.org took 1.33514404296875e-05s
INFO | --- Analysis for semanticweb-org took 22.986481189727783s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.08051753044128418s
Availability | VoID file availability check for Semantic CrunchBase took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.48111867904663086s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.022714853286743164s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0011243820190429688s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 8.58306884765625e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.1682510375976562e-05s
INFO | --- Analysis for semsol-crunchbase took 3.080880641937256s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2513144016265869s
Availability | VoID file availability check for SentimentWortschatz took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2962160110473633s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.124641418457031e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.1920928955078125e-05s
INFO | --- Analysis for sentiws took 4.308809757232666s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.079298496246338s
Availability | VoID file availability check for seoul-bike-data took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.35120177268981934s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.022193193435668945s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 2.9325485229492188e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.239776611328125e-05s
INFO | --- Analysis for seoul-bike-data took 72.98924469947815s
Availability | SPARQL endpoint availability check for Serendipity took 3.966937303543091s
Availability | VoID file availability check for Serendipity took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Serendipity took 0.32831859588623047s
Reputation | Calculation of the PageRank for Serendipity took 0.023174524307250977s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.128715515136719e-05s
Believability | Calculation of trust value for Serendipity took 1.2159347534179688e-05s
INFO | --- Analysis for serendipity took 10.640530586242676s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 0.00015926361083984375s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.3001394271850586s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.170967102050781e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.2874603271484375e-05s
INFO | --- Analysis for Sherry_Wine took 2.996654748916626s
Availability | SPARQL endpoint availability check for Sherry Wine took 8.869171142578125e-05s
Availability | VoID file availability check for Sherry Wine took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.3015787601470947s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.218650817871094e-05s
Believability | Calculation of trust value for Sherry Wine took 9.775161743164062e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.7083818912506104s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.20100069046020508s
Availability | VoID file availability check for Shoah victims? names took 0.31795334815979004s
Extra | Recovery of all triples for Shoah victims? names took 0.9483435153961182s
Performance | Total latancy measurement for Shoah victims? names took 0.3804600238800049s
Amount of data | Number of triples check for Shoah victims? names took 1.3377110958099365s
Interoperability | New terms check for Shoah victims? names took 1.6657178401947021s
Versatility | Languages check for Shoah victims? names took 18.84106421470642s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.946603536605835s
Security | Check HTTPS for Shoah victims? names took 0.17755579948425293s
Interpretability | RDF structures check for Shoah victims? names took 0.24613261222839355s
Versatility | Serialization formats check for Shoah victims? names took 0.26280665397644043s
Availability | RDF dump link check for Shoah victims? names took 0.17479872703552246s
License | MR license check for Shoah victims? names took 0.31320929527282715s
License | HR license check for Shoah victims? names took 8.842777252197266s
Amount of data | Number of property check for Shoah victims? names took 0.12725591659545898s
Understandability | Number of label check for Shoah victims? names took 1.0194706916809082s
Understandability | URI regex check for Shoah victims? names took 0.4169938564300537s
Understandability | Vocabs check for Shoah victims? names took 0.12826251983642578s
Verifiability | Authors check for Shoah victims? names took 0.1573023796081543s
Verifiability | Publishers check for Shoah victims? names took 0.15076494216918945s
Performance | Throughput check for Shoah victims? names took 10.778117895126343s
Amount of data | Check the number of entities for Shoah victims? names took 7.152557373046875e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.07663273811340332s
Interlinking | sameAs chians check for Shoah victims? names took 0.13865184783935547s
Interlinking | skos check for Shoah victims? names took 0.19923877716064453s
Interlinking | skos check for Shoah victims? names took 0.07182860374450684s
Timeliness | dataset update frequency check for Shoah victims? names took 0.196183443069458s
Currency | Creation date check for Shoah victims? names took 0.18113088607788086s
Currency | Modification date check for Shoah victims? names took 0.20090293884277344s
Rep.Conc. | URIs length for Shoah victims? names took 2.485111713409424s
Interoperability | New vocabularies check for Shoah victims? names took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.08530354499816895s
Accuracy | Check Functional Property for Shoah victims? names took 0.0975959300994873s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.08354449272155762s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.3425612449645996s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02770543098449707s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.028788328170776367s
Consistency | Disjoint class check for Shoah victims? names took 0.1760096549987793s
Consistency | Check Misplaced properties for Shoah victims? names took 2.1434731483459473s
Consistency | Misplaced classes for Shoah victims? names took 0.18640613555908203s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.745558500289917s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.295884132385254s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.022834539413452s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.034809112548828125s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.14148592948913574s
Security | Sign check for Shoah victims? names took 0.3406519889831543s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1025.9954767227173s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.5139443874359131s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.021667003631591797s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 2.1457672119140625e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.1682510375976562e-05s
INFO | --- Analysis for shoah-victims-names took 1143.8706884384155s
Availability | SPARQL endpoint availability check for Person took 4.267692565917969e-05s
Availability | VoID file availability check for Person took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Person took 0.33918237686157227s
Reputation | Calculation of the PageRank for Person took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for Person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Person took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Person took 2.9087066650390625e-05s
Believability | Calculation of trust value for Person took 1.0728836059570312e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.6835856437683105s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 9.322166442871094e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.3099033832550049s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.86102294921875e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 6.9141387939453125e-06s
INFO | --- Analysis for Shutterstock took 2.7622766494750977s
Availability | SPARQL endpoint availability check for SIMPLE took 4.291534423828125e-05s
Availability | VoID file availability check for SIMPLE took 0.0004024505615234375s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.29787182807922363s
Reputation | Calculation of the PageRank for SIMPLE took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 3.647804260253906e-05s
Believability | Calculation of trust value for SIMPLE took 9.059906005859375e-06s
INFO | --- Analysis for simple took 8.337387084960938s
Availability | SPARQL endpoint availability check for SITC-V4 took 26.419719219207764s
Availability | VoID file availability check for SITC-V4 took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.2876887321472168s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.38690185546875e-05s
Believability | Calculation of trust value for SITC-V4 took 5.0067901611328125e-06s
INFO | --- Analysis for sitc-v4 took 125.2359185218811s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.3392181396484375e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.2696695327758789s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.3392181396484375e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 8.106231689453125e-06s
INFO | --- Analysis for sli_galnet_rdf took 12.874430179595947s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.291534423828125e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.29363107681274414s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.075599670410156e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 7.3909759521484375e-06s
INFO | --- Analysis for slideshare2rdf took 2.689548969268799s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.5434105396270752s
Availability | VoID file availability check for Linked Stage Graph took 0.0002675056457519531s
Extra | Recovery of all triples for Linked Stage Graph took 1.9736332893371582s
Performance | Total latancy measurement for Linked Stage Graph took 1.248434066772461s
Amount of data | Number of triples check for Linked Stage Graph took 0.2784609794616699s
Interoperability | New terms check for Linked Stage Graph took 1.5766289234161377s
Versatility | Languages check for Linked Stage Graph took 0.7057948112487793s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.3040003776550293s
Security | Check HTTPS for Linked Stage Graph took 0.16156005859375s
Interpretability | RDF structures check for Linked Stage Graph took 0.6026618480682373s
Versatility | Serialization formats check for Linked Stage Graph took 0.4112839698791504s
Availability | RDF dump link check for Linked Stage Graph took 0.25650811195373535s
License | MR license check for Linked Stage Graph took 0.5855484008789062s
License | HR license check for Linked Stage Graph took 1.8542068004608154s
Amount of data | Number of property check for Linked Stage Graph took 0.2465059757232666s
Understandability | Number of label check for Linked Stage Graph took 0.8563296794891357s
Understandability | URI regex check for Linked Stage Graph took 0.6788833141326904s
Understandability | Vocabs check for Linked Stage Graph took 0.3746204376220703s
Verifiability | Authors check for Linked Stage Graph took 0.27295804023742676s
Verifiability | Publishers check for Linked Stage Graph took 0.23240017890930176s
Performance | Throughput check for Linked Stage Graph took 10.966982126235962s
Amount of data | Check the number of entities for Linked Stage Graph took 3.218650817871094e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.2822542190551758s
Interlinking | sameAs chians check for Linked Stage Graph took 0.3901386260986328s
Interlinking | skos check for Linked Stage Graph took 0.3144876956939697s
Interlinking | skos check for Linked Stage Graph took 0.28432393074035645s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.46535348892211914s
Currency | Creation date check for Linked Stage Graph took 0.5312082767486572s
Currency | Modification date check for Linked Stage Graph took 0.5291645526885986s
Rep.Conc. | URIs length for Linked Stage Graph took 1.6254405975341797s
Interoperability | New vocabularies check for Linked Stage Graph took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.2587113380432129s
Accuracy | Check Functional Property for Linked Stage Graph took 0.5091793537139893s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.47495603561401367s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.8365883827209473s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.024249792098999023s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.027984142303466797s
Consistency | Disjoint class check for Linked Stage Graph took 0.28636980056762695s
Consistency | Check Misplaced properties for Linked Stage Graph took 1.089252233505249s
Consistency | Misplaced classes for Linked Stage Graph took 0.6278383731842041s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.0796008110046387s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.2661113739013672s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.8198778629302979s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.026754140853881836s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.5931527614593506s
Security | Sign check for Linked Stage Graph took 0.6640686988830566s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 1296.9690985679626s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.7669768333435059s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.021394729614257812s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 6.580352783203125e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.52587890625e-05s
INFO | --- Analysis for slod took 1366.8816647529602s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.5079512596130371s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0005218982696533203s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 116.34447145462036s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9852790832519531s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.498008728027344s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.16078233718872s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.20592498779297s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.290867328643799s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.34798717498779297s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 9.116233825683594s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.36989712715148926s
License | MR license check for Smart Points Of Interest @PSNC took 1.0182149410247803s
License | HR license check for Smart Points Of Interest @PSNC took 300.253835439682s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.20433950424194336s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.5569920539855957s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 1.0577588081359863s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.5442862510681152s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.22911405563354492s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.23906207084655762s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.202601194381714s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 0.00018644332885742188s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.20741605758666992s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.20246481895446777s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.5062582492828369s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.43611598014831543s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 5.737943887710571s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.48951101303100586s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.23126530647277832s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 99.35760593414307s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.20847249031066895s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.45322680473327637s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.45613694190979004s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 31.860322952270508s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.677478790283203s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.6069252490997314s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.19837045669555664s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 86.54422807693481s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.26163911819458s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 35.77540898323059s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.320486068725586s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 86.9040355682373s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.791733503341675s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.6002933979034424s
Security | Sign check for Smart Points Of Interest @PSNC took 0.7727046012878418s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 9.457395315170288s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.5569703578948975s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02135467529296875s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010204315185546875s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for Smart_POI_dataset took 2213.4262924194336s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.709944248199463s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.28639864921569824s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02204418182373047s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 4.3392181396484375e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.430511474609375e-05s
INFO | --- Analysis for smartlink took 14.038375854492188s
Availability | SPARQL endpoint availability check for SNIK took 0.3906288146972656s
Availability | VoID file availability check for SNIK took 0.0008237361907958984s
Extra | Recovery of all triples for SNIK took 3.0793395042419434s
Performance | Total latancy measurement for SNIK took 0.952744722366333s
Amount of data | Number of triples check for SNIK took 0.17526865005493164s
Interoperability | New terms check for SNIK took 1.4891281127929688s
Versatility | Languages check for SNIK took 0.23000311851501465s
Interpretability | Number of blank nodes check for SNIK took 0.1879897117614746s
Interpretability | RDF structures check for SNIK took 0.21266794204711914s
Versatility | Serialization formats check for SNIK took 0.20912790298461914s
Availability | RDF dump link check for SNIK took 0.2019636631011963s
License | MR license check for SNIK took 0.2097012996673584s
License | HR license check for SNIK took 0.2136399745941162s
Amount of data | Number of property check for SNIK took 0.18888497352600098s
Understandability | Number of label check for SNIK took 0.21967124938964844s
Understandability | URI regex check for SNIK took 0.38411545753479004s
Understandability | Vocabs check for SNIK took 0.19280552864074707s
Verifiability | Authors check for SNIK took 0.18159198760986328s
Verifiability | Publishers check for SNIK took 0.18074655532836914s
Amount of data | Check the number of entities for SNIK took 8.368492126464844e-05s
Verifiability | Contribs. check for SNIK took 0.20607376098632812s
Interlinking | sameAs chians check for SNIK took 0.17449331283569336s
Interlinking | skos check for SNIK took 0.1728076934814453s
Interlinking | skos check for SNIK took 0.18942499160766602s
Timeliness | dataset update frequency check for SNIK took 0.1982128620147705s
Currency | Creation date check for SNIK took 0.3723294734954834s
Currency | Modification date check for SNIK took 0.40364813804626465s
Rep.Conc. | URIs length for SNIK took 1.4082238674163818s
Interoperability | New vocabularies check for SNIK took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.20013976097106934s
Accuracy | Check Functional Property for SNIK took 0.16988682746887207s
Accuracy | Check Inverse Functional Property for SNIK took 0.20301246643066406s
Accuracy | Check Empty annotation labels for SNIK took 0.6342689990997314s
Accuracy | Check White space in annotation for SNIK took 0.027153730392456055s
Accuracy | Check Datatype consistency for SNIK took 0.21757102012634277s
Consistency | Disjoint class check for SNIK took 0.16945385932922363s
Consistency | Check Misplaced properties for SNIK took 0.7235991954803467s
Consistency | Misplaced classes for SNIK took 0.6786849498748779s
Consistency | Check Ontology hijacking for SNIK took 1.8252034187316895s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.244415044784546s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.4945619106292725s
Conciseness | Check Extensional conciseness for SNIK took 0.15602326393127441s
Conciseness | Check Intensional conciseness for SNIK took 0.3206491470336914s
Security | Sign check for SNIK took 0.20472335815429688s
Availability | Check URIs Dereferenciability for SNIK took 2070.0665345191956s
Completeness | Calculation of interlinking completeness for SNIK took 6.116245985031128s
Reputation | Calculation of the PageRank for SNIK took 0.02184152603149414s
Interlinking | Calculation of Degree of Connection for SNIK took 6.532669067382812e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0009832382202148438s
Interlinking | Calculation of Clustering coefficient for SNIK took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.9073486328125e-06s
Believability | Calculation of trust value for SNIK took 7.867813110351562e-06s
INFO | --- Analysis for snik took 2138.6030809879303s
Availability | SPARQL endpoint availability check for SocialLink took 1.0493478775024414s
Availability | VoID file availability check for SocialLink took 0.00039076805114746094s
Completeness | Calculation of interlinking completeness for SocialLink took 0.28576040267944336s
Reputation | Calculation of the PageRank for SocialLink took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for SocialLink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.510185241699219e-05s
Believability | Calculation of trust value for SocialLink took 1.3113021850585938e-05s
INFO | --- Analysis for SocialLink took 26.15534996986389s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 9.179115295410156e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0014750957489013672s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.30533766746520996s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.337860107421875e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.2874603271484375e-05s
INFO | --- Analysis for SocialRoles took 10.179843425750732s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.24585556983947754s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007190704345703125s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 31.370749473571777s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 1.5324196815490723s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.19646024703979492s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.5032289028167725s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.4208698272705078s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.1923213005065918s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.36728644371032715s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.13544082641601562s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.12183260917663574s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.8256723880767822s
License | MR license check for Social Semantic Web Thesaurus took 0.14389443397521973s
License | HR license check for Social Semantic Web Thesaurus took 0.11673712730407715s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.13402652740478516s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.14564037322998047s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.1981196403503418s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.11891365051269531s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.12784385681152344s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.12054872512817383s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.305821657180786s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 9.417533874511719e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.1394033432006836s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.9520082473754883s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.12125134468078613s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.09444117546081543s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.11548662185668945s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.229844331741333s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.2843289375305176s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.544536828994751s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 0.7317430973052979s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.12736296653747559s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.10472631454467773s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09976768493652344s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.5311532020568848s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.015941858291625977s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.10590291023254395s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.3665196895599365s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.11293864250183105s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.2085719108581543s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.5120158195495605s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0001800060272216797s
Security | Sign check for Social Semantic Web Thesaurus took 0.0916895866394043s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 169.3930652141571s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.40874481201171875s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.72747802734375e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.6095929145812988s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 445.5978789329529s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3230326175689697s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0002446174621582031s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 106.4602963924408s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9923813343048096s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.999372720718384s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.215779781341553s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.18465971946716s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.062253475189209s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20020604133605957s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.478864908218384s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21388649940490723s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3226277828216553s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.18266105651855s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19807982444763184s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2328920364379883s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.7439877986907959s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5050370693206787s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1861572265625s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.24930214881896973s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.557672262191772s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.250640869140625e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2133467197418213s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19795584678649902s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.42681336402893066s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4409952163696289s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 6.185729742050171s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4775395393371582s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.23337197303771973s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 149.03820204734802s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19991517066955566s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2088778018951416s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1848151683807373s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 35.314592123031616s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6839139461517334s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6466825008392334s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1988065242767334s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 86.58260798454285s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.305239200592041s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 30.99531626701355s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.4021315574645996s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 88.06600093841553s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.8447041511535645s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5465071201324463s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19761443138122559s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.277669906616211s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5151891708374023s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.020994901657104492s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for Soil_maps took 2240.776757955551s
Availability | SPARQL endpoint availability check for terrorrist ontology took 4.291534423828125e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.2991366386413574s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.1444091796875e-05s
INFO | --- Analysis for somya_omer took 2.6609411239624023s
Availability | SPARQL endpoint availability check for Sonclubcx took 8.869171142578125e-05s
Availability | VoID file availability check for Sonclubcx took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.39592432975769043s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.3113021850585938e-05s
Believability | Calculation of trust value for Sonclubcx took 1.0967254638671875e-05s
INFO | --- Analysis for sonclubcx took 4.338911294937134s
Availability | SPARQL endpoint availability check for SORS took 8.749961853027344e-05s
Availability | VoID file availability check for SORS took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for SORS took 0.33132481575012207s
Reputation | Calculation of the PageRank for SORS took 0.02029252052307129s
Interlinking | Calculation of Degree of Connection for SORS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SORS took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for SORS took 4.863739013671875e-05s
Believability | Calculation of trust value for SORS took 8.58306884765625e-06s
INFO | --- Analysis for sors took 12.882875204086304s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 9.131431579589844e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.30046987533569336s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.989738464355469e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.0728836059570312e-05s
INFO | --- Analysis for southampton-ac-uk took 4.174523591995239s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.3111023902893066s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.28157496452331543s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 7.3909759521484375e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.717082262039185s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.38690185546875e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2815992832183838s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.417533874511719e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 7.867813110351562e-06s
INFO | --- Analysis for southampton-ecs-eprints took 2.8296682834625244s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5103781223297119s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0002684593200683594s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 161.61052656173706s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.236173152923584s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.166374921798706s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.0450026988983154s
Versatility | Languages check for Spanish Linguistic Datasets took 44.69939136505127s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.2071068286895752s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.14494109153747559s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.2945375442504883s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.32326817512512207s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.28508639335632324s
License | MR license check for Spanish Linguistic Datasets took 0.3077974319458008s
License | HR license check for Spanish Linguistic Datasets took 0.4241485595703125s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.2984142303466797s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.33394622802734375s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5981359481811523s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.29357004165649414s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.2857646942138672s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2879824638366699s
Performance | Throughput check for Spanish Linguistic Datasets took 11.238372564315796s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.605552673339844e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.2903873920440674s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.30044078826904297s
Interlinking | skos check for Spanish Linguistic Datasets took 0.28536319732666016s
Interlinking | skos check for Spanish Linguistic Datasets took 0.22298002243041992s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.28395771980285645s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5709028244018555s
Currency | Modification date check for Spanish Linguistic Datasets took 0.621370792388916s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 58.53647589683533s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.3292815685272217s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.30074310302734375s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.2861366271972656s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9874894618988037s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010383844375610352s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.650409698486328s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.320711612701416s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.726978302001953s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.389316082000732s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 43.93931007385254s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.4452564716339111s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.689801931381226s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.973965644836426s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.31278419494628906s
Security | Sign check for Spanish Linguistic Datasets took 0.27155113220214844s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 10.155510187149048s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.43462681770324707s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021384000778198242s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.6226043701171875e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.3828277587890625e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 412.1429977416992s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.05138373374938965s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.296006441116333s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.7206878662109375e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 7.3909759521484375e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.773211717605591s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.1961669921875e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2852909564971924s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.344650268554688e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.049041748046875e-05s
INFO | --- Analysis for springernaturescigraph took 3.2712864875793457s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.363059997558594e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.28078603744506836s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.956390380859375e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 6.4373016357421875e-06s
INFO | --- Analysis for srcmf took 9.10690951347351s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.34752941131591797s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.00026679039001464844s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.2274928092956543s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.7247400283813477s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.14900898933410645s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.3653182983398438s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.16428041458129883s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.15602707862854004s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.08751678466796875s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.15310215950012207s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.14152145385742188s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.14714884757995605s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.1550898551940918s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.14860820770263672s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.16161251068115234s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.14770269393920898s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.29309797286987305s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.1512603759765625s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.14074063301086426s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.14035725593566895s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 10.304210424423218s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 3.886222839355469e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.15375947952270508s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.14083647727966309s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.15750694274902344s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.1415715217590332s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.15590333938598633s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.28996777534484863s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.2893941402435303s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.44535255432128906s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.1388711929321289s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.15411925315856934s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.15435791015625s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.13672947883605957s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.00013756752014160156s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.030972003936767578s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.13448286056518555s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.2854428291320801s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.19012045860290527s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.4238910675048828s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.2537589073181152s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.415480136871338s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.019771814346313477s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.1482081413269043s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.1394503116607666s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 344.5978319644928s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.3695216178894043s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.021307945251464844s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 2.6226043701171875e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.0967254638671875e-05s
INFO | --- Analysis for ssf took 384.5300621986389s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.458427429199219e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.31105470657348633s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.022562265396118164s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.647804260253906e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.0967254638671875e-05s
INFO | --- Analysis for st-andrews-resource-lists took 3.141317129135132s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.608268737792969e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.31012725830078125s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.552436828613281e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.106231689453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.2869160175323486s
Availability | SPARQL endpoint availability check for Stammbuch took 5.412101745605469e-05s
Availability | VoID file availability check for Stammbuch took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.27194690704345703s
Reputation | Calculation of the PageRank for Stammbuch took 0.021799564361572266s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.2901763916015625e-05s
Believability | Calculation of trust value for Stammbuch took 1.2159347534179688e-05s
INFO | --- Analysis for Stammbuch took 2.911353349685669s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.439192771911621s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2989187240600586s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.021908998489379883s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00011515617370605469s
Believability | Calculation of trust value for statistics.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.6600501537323s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2788574695587158s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.021265268325805664s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-1w6-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-1w6-org took 3.1453917026519775s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 0.0001125335693359375s
Availability | VoID file availability check for statusnet-20100-org took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.30894017219543457s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.023276805877685547s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-20100-org took 2.8419382572174072s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.27472591400146484s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 8.034706115722656e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 3.0628128051757812s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 0.0001251697540283203s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.29108309745788574s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.021368026733398438s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.106231689453125e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.728074073791504s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 9.036064147949219e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2971067428588867s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 8.845329284667969e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.800978899002075s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.3038504123687744s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02751016616821289s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.0001239776611328125s
Believability | Calculation of trust value for statusnet-bka-li took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-bka-li took 12.819785833358765s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 0.00010728836059570312s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.3064603805541992s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.9577484130859375e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.768376111984253s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 9.131431579589844e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.30439114570617676s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020926237106323242s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.839897155761719e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-ced117-net took 4.629597187042236s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 9.059906005859375e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.29802846908569336s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.340576171875e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.980203151702881s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 5.2928924560546875e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.3359262943267822s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.02344822883605957s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011682510375976562s
Believability | Calculation of trust value for statusnet-chromic-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-chromic-org took 2.9705190658569336s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.30942749977111816s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.772445678710938e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.243825197219849s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 9.393692016601562e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.3058021068572998s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.02147984504699707s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.626678466796875e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 2.7518789768218994s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 8.7738037109375e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2919132709503174s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.021188974380493164s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.033348083496094e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 4.744529724121094e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.4793477058410645s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 0.00010943412780761719s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.3289608955383301s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02091526985168457s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010609626770019531s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.8870203495025635s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 9.72747802734375e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2995457649230957s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.021886587142944336s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.389617919921875e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 2.8371810913085938e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.751019239425659s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 8.988380432128906e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0007653236389160156s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.3183410167694092s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-doomicile-de took 4.917433261871338s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.30484771728515625s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-dtdns-net took 2.8563435077667236s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.28492259979248047s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.02109050750732422s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.7670135498046875e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.6830177307128906s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.2902204990386963s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.021491527557373047s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.2479248046875e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-exdc-net took 12.778252840042114s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.29805874824523926s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.298324584960938e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-fcac-com took 3.2617037296295166s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 8.96453857421875e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2896902561187744s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.021555185317993164s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.555152893066406e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 3.483119487762451s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 8.821487426757812e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.3059990406036377s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.022133588790893555s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018072128295898438s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-fragdev-com took 3.6943180561065674s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0010294914245605469s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.3357234001159668s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.022639751434326172s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-freelish-us took 3.1808860301971436s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 8.988380432128906e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.30520153045654297s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.0001049041748046875s
Believability | Calculation of trust value for statusnet-gegeweb-org took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.803435802459717s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.29950809478759766s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.021797895431518555s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.510185241699219e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-glou-org took 2.689817428588867s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 0.00010132789611816406s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.32828378677368164s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.02073383331298828s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0010576248168945312s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00015687942504882812s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 2.759167194366455s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.28936195373535156s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.021703243255615234s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010466575622558594s
Believability | Calculation of trust value for statusnet-hackerposse-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 3.2676210403442383s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0013203620910644531s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.29326415061950684s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02086162567138672s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 5.030632019042969e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.849327564239502s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.3409543037414551s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.02101588249206543s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.894371032714844e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.065199136734009s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.32346367835998535s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.023090600967407227s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.7576904296875s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 8.821487426757812e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2872328758239746s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.022129058837890625s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.172325134277344e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-integralblue-com took 2.9099655151367188s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.30367445945739746s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.021062135696411133s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.626678466796875e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.693036794662476s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 0.00010442733764648438s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2825472354888916s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.0001163482666015625s
Believability | Calculation of trust value for statusnet-jonkman-ca took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 5.176314353942871s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.30886030197143555s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.021684646606445312s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 0.00010013580322265625s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.729614734649658s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.3185083866119385s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.021282672882080078s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.824110984802246s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 9.083747863769531e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2801980972290039s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.00543212890625e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.6964612007141113s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.3000025749206543s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.0221865177154541s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.43865966796875e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.7190141677856445s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 8.845329284667969e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2988908290863037s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 3.031822681427002s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2670114040374756s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 3.020190715789795s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 9.083747863769531e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.33971548080444336s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.322166442871094e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 3.3986124992370605s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 7.748603820800781e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.30579590797424316s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.022612810134887695s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011563301086425781s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.7585103511810303s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 8.96453857421875e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.27695488929748535s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-ludost-net took 4.043271541595459s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.29819440841674805s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00010132789611816406s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.769782543182373s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.29865336418151855s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.021297454833984375s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0009794235229492188s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 6.985664367675781e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.6622753143310547s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2874267101287842s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.021747112274169922s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00015664100646972656s
Believability | Calculation of trust value for statusnet-macno-org took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-macno-org took 3.0826334953308105s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.319791316986084s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 8.0108642578125e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 5.817413330078125e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 3.105628728866577s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.31647801399230957s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020635604858398438s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 7.62939453125e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.50841212272644s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 0.00012803077697753906s
Availability | VoID file availability check for statusnet-morphtown-de took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.28806495666503906s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02269601821899414s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015926361083984375s
Believability | Calculation of trust value for statusnet-morphtown-de took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-morphtown-de took 3.1535449028015137s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.27895331382751465s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.021597862243652344s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.799003601074219e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 3.173007011413574s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 9.34600830078125e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.30626893043518066s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02113819122314453s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.8650970458984375e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-mulestable-net took 2.660446882247925s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.3051412105560303s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.022612810134887695s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.412101745605469e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.950900077819824s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.3050088882446289s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010800361633300781s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.674598217010498s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.30806612968444824s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020906925201416016s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.698204040527344e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 3.00858998298645s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.28235626220703125s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020985126495361328s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.681877851486206s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.299302339553833s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.021964311599731445s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.58306884765625e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.6981160640716553s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 5.125999450683594e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.30500149726867676s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.021001577377319336s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-panda-id-au took 3.3360748291015625s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2903134822845459s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.02097153663635254s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 0.00011920928955078125s
Believability | Calculation of trust value for statusnet-piana-eu took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.724790096282959s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0008885860443115234s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.26224207878112793s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.021991491317749023s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.939338684082031e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.784207582473755s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 9.131431579589844e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2934906482696533s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00022935867309570312s
Believability | Calculation of trust value for statusnet-postblue-info took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.908507823944092s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.8160552978515625e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.4445016384124756s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.022852182388305664s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.604194641113281e-05s
Believability | Calculation of trust value for statusnet-progval-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-progval-net took 22.896177291870117s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.3264501094818115s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020997047424316406s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.0001220703125s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-qdnx-org took 3.1611340045928955s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.001255035400390625s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2828388214111328s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-qth-fr took 3.555842399597168s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.26616477966308594s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00024366378784179688s
Believability | Calculation of trust value for statusnet-quitter-se took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-quitter-se took 35.486647844314575s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.259807825088501s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.0001087188720703125s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.8415114879608154s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.3143792152404785s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.021025657653808594s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-recit-org took 13.029163599014282s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.27615880966186523s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02223992347717285s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00014638900756835938s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.5118942260742188s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.3004148006439209s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.416175842285156e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-samnoble-org took 5.2233359813690186s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.28371524810791016s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.021921396255493164s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.058547973632812e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.905552625656128s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 9.679794311523438e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.27332091331481934s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02231144905090332s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.965896606445312e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 2.7701356410980225s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.31060123443603516s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.73540997505188s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 6.723403930664062e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.27593016624450684s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.022171735763549805s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.081031799316406e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.4801206588745117s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 8.845329284667969e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.27940869331359863s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0008146762847900391s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.0002903938293457031s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 3.3463187217712402s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 5.626678466796875e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2832045555114746s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010561943054199219s
Believability | Calculation of trust value for statusnet-somsants-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.7017579078674316s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.33144545555114746s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.021185636520385742s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0010600090026855469s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001659393310546875s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-soucy-cc took 4.486219167709351s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.29601216316223145s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-spip-org took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-spip-org took 3.702582359313965s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2653622627258301s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.02246260643005371s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-spraci-org took 5.630221605300903s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.27634334564208984s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.02197098731994629s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011467933654785156s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 5.691927194595337s
Availability | SPARQL endpoint availability check for statusnet-status-net took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.288055419921875s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00023174285888671875s
Believability | Calculation of trust value for statusnet-status-net took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-status-net took 3.8962857723236084s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 9.298324584960938e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2629365921020508s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0009944438934326172s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.7579450607299805s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.27318572998046875s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.5367431640625e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.7866146564483643s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.26401495933532715s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02150416374206543s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012993812561035156s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.8064191341400146s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2891082763671875s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.023543119430541992s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.486343383789062e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-thornton2-com took 8.159520626068115s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2942948341369629s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00011277198791503906s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 3.0999093055725098s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.3181426525115967s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.022467613220214844s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.1484832763671875e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-tl1n-com took 4.202132701873779s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2775146961212158s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.021165132522583008s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.961822509765625e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.8958523273468018s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2892117500305176s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 4.124641418457031e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.5055551528930664s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 8.821487426757812e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.27671265602111816s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020890474319458008s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for steak took 2.9878270626068115s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 8.606910705566406e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.31970906257629395s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.021530866622924805s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.698204040527344e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.2159347534179688e-05s
INFO | --- Analysis for stitch-rameau took 4.399362087249756s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.8699295520782471s
Availability | VoID file availability check for Stone Tech Square took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2771012783050537s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.022452354431152344s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.3113021850585938e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.2159347534179688e-05s
INFO | --- Analysis for stone-tech-square-data took 4.538433074951172s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.44362425804138184s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0007412433624267578s
Extra | Recovery of all triples for STW Thesaurus for Economics took 21.722108125686646s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1455647945404053s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.7120411396026611s
Interoperability | New terms check for STW Thesaurus for Economics took 1.5873360633850098s
Versatility | Languages check for STW Thesaurus for Economics took 1.6075122356414795s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5329034328460693s
Security | Check HTTPS for STW Thesaurus for Economics took 0.16346025466918945s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.25093960762023926s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.26349830627441406s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.24352502822875977s
License | MR license check for STW Thesaurus for Economics took 0.2604680061340332s
License | HR license check for STW Thesaurus for Economics took 2.5700812339782715s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2754373550415039s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6366348266601562s
Understandability | URI regex check for STW Thesaurus for Economics took 0.48148131370544434s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.2908134460449219s
Verifiability | Authors check for STW Thesaurus for Economics took 0.2447826862335205s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2455921173095703s
Performance | Throughput check for STW Thesaurus for Economics took 10.930832147598267s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7296226024627686s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2782783508300781s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2975325584411621s
Interlinking | skos check for STW Thesaurus for Economics took 0.36115598678588867s
Interlinking | skos check for STW Thesaurus for Economics took 0.3086817264556885s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.23121190071105957s
Currency | Creation date check for STW Thesaurus for Economics took 0.5036871433258057s
Currency | Modification date check for STW Thesaurus for Economics took 0.5099494457244873s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.4200756549835205s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 3.665865182876587s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.263577938079834s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.23227787017822266s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.25205063819885254s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 4.636146306991577s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0451433658599854s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.3471925258636475s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.2525758743286133s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2316703796386719s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.7437329292297363s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.337597131729126s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.319135904312134s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.7255349159240723s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.23708176612854004s
Security | Sign check for STW Thesaurus for Economics took 0.29898738861083984s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 5.103377819061279s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.29127025604248047s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0009794235229492188s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00013446807861328125s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 3.40122127532959s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.621246337890625e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 108.94618558883667s
Availability | SPARQL endpoint availability check for SudershanTech took 9.083747863769531e-05s
Availability | VoID file availability check for SudershanTech took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.3096187114715576s
Reputation | Calculation of the PageRank for SudershanTech took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.218650817871094e-05s
Believability | Calculation of trust value for SudershanTech took 1.2874603271484375e-05s
INFO | --- Analysis for SudershanTech took 2.9605634212493896s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.8030352592468262s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.3080151081085205s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.021799564361572266s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 5.054473876953125e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.3113021850585938e-05s
INFO | --- Analysis for sudocfr took 11.647396564483643s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0084166526794434s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006592273712158203s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 22.431435585021973s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.5835964679718018s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.4576294422149658s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.8083255290985107s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.5293800830841064s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.1683290004730225s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5211060047149658s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.530646800994873s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5487649440765381s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5373046398162842s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 8.148882627487183s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5587906837463379s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.7020556926727295s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.0716462135314941s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5271024703979492s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5495939254760742s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.549086332321167s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.700354814529419s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 7.033348083496094e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.529310941696167s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5888998508453369s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5981571674346924s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6107850074768066s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5276765823364258s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0824100971221924s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.0938515663146973s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 38.40264844894409s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.6024181842803955s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5127625465393066s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5254526138305664s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 2.973315954208374s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.37850069999694824s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5587368011474609s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 29.216942071914673s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.459324598312378s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.45834612846375s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 25.297146797180176s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.097486972808838s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.5458242893218994s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5298857688903809s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4526.823858737946s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 5.708925724029541s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02155470848083496s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 9.322166442871094e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 8.606910705566406e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 5.245208740234375e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.0251998901367188e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8075.904766559601s
Availability | SPARQL endpoint availability check for Surge Radio took 9.465217590332031e-05s
Availability | VoID file availability check for Surge Radio took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.2937648296356201s
Reputation | Calculation of the PageRank for Surge Radio took 0.021675586700439453s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.559226989746094e-05s
Believability | Calculation of trust value for Surge Radio took 1.3113021850585938e-05s
INFO | --- Analysis for surge-radio took 3.7555699348449707s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 0.00012683868408203125s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.3312387466430664s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.021335363388061523s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.0994415283203125e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.1205673217773438e-05s
INFO | --- Analysis for SWAT took 89.59324383735657s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 8.630752563476562e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4411125183105469s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.34269022941589355s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 8.893013000488281e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.2636184692382812e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.0506768226623535s
Availability | SPARQL endpoint availability check for SweFN-RDF took 0.9939634799957275s
Availability | VoID file availability check for SweFN-RDF took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.31712841987609863s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.021045446395874023s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.8623809814453125e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.0967254638671875e-05s
INFO | --- Analysis for swefn-rdf took 6.034809827804565s
Availability | SPARQL endpoint availability check for SwetoDblp took 9.131431579589844e-05s
Availability | VoID file availability check for SwetoDblp took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.290790319442749s
Reputation | Calculation of the PageRank for SwetoDblp took 0.021137714385986328s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 4.4345855712890625e-05s
Believability | Calculation of trust value for SwetoDblp took 1.3113021850585938e-05s
INFO | --- Analysis for sweto-dblp took 23.090741872787476s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.565549373626709s
Availability | VoID file availability check for Swift Vocabulary took 0.0007085800170898438s
Extra | Recovery of all triples for Swift Vocabulary took 2.2488906383514404s
Performance | Total latancy measurement for Swift Vocabulary took 1.1263794898986816s
Amount of data | Number of triples check for Swift Vocabulary took 0.20857930183410645s
Interoperability | New terms check for Swift Vocabulary took 1.4240474700927734s
Versatility | Languages check for Swift Vocabulary took 0.18351268768310547s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.16886377334594727s
Interpretability | RDF structures check for Swift Vocabulary took 0.16191768646240234s
Versatility | Serialization formats check for Swift Vocabulary took 0.17811179161071777s
Availability | RDF dump link check for Swift Vocabulary took 0.31041550636291504s
License | MR license check for Swift Vocabulary took 0.22939848899841309s
License | HR license check for Swift Vocabulary took 0.2097914218902588s
Amount of data | Number of property check for Swift Vocabulary took 0.21013474464416504s
Understandability | Number of label check for Swift Vocabulary took 0.21582794189453125s
Understandability | URI regex check for Swift Vocabulary took 0.41498732566833496s
Understandability | Vocabs check for Swift Vocabulary took 0.20802664756774902s
Verifiability | Authors check for Swift Vocabulary took 0.19474005699157715s
Verifiability | Publishers check for Swift Vocabulary took 0.22620439529418945s
Performance | Throughput check for Swift Vocabulary took 10.706281661987305s
Amount of data | Check the number of entities for Swift Vocabulary took 7.510185241699219e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.22892284393310547s
Interlinking | sameAs chians check for Swift Vocabulary took 0.20880532264709473s
Interlinking | skos check for Swift Vocabulary took 0.21127939224243164s
Interlinking | skos check for Swift Vocabulary took 0.20916962623596191s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.1928551197052002s
Currency | Creation date check for Swift Vocabulary took 0.44713902473449707s
Currency | Modification date check for Swift Vocabulary took 0.43963623046875s
Rep.Conc. | URIs length for Swift Vocabulary took 0.7652902603149414s
Interoperability | New vocabularies check for Swift Vocabulary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.2061769962310791s
Accuracy | Check Functional Property for Swift Vocabulary took 0.18727421760559082s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.18787813186645508s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.36609768867492676s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0020956993103027344s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03623223304748535s
Consistency | Disjoint class check for Swift Vocabulary took 0.20545005798339844s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.4764883518218994s
Consistency | Misplaced classes for Swift Vocabulary took 0.28172922134399414s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.5179708003997803s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.2583048343658447s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.4248738288879395s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.026592016220092773s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.16724658012390137s
Security | Sign check for Swift Vocabulary took 0.1701204776763916s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 955.8583974838257s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.6909644603729248s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.9073486328125e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.4781951904296875e-05s
INFO | --- Analysis for Swift took 1002.6125564575195s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 9.1552734375e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0007703304290771484s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.3212547302246094s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.022438526153564453s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.075599670410156e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.2874603271484375e-05s
INFO | --- Analysis for symptoms-in-chinese took 53.36423420906067s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.3742704391479492s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0007910728454589844s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.44715285301208496s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.9026401042938232s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 27.84456777572632s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.68908953666687s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.18272805213928223s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.1618905067443848s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.12151455879211426s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.41020798683166504s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.1819322109222412s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.18761467933654785s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.28972744941711426s
License | HR license check for National Digital Data Archive of Hungary (partial) took 53.42578935623169s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.4381692409515381s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 32.576186418533325s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3538093566894531s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.20799684524536133s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.19792604446411133s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.19172978401184082s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.70653748512268s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.128715515136719e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.926616907119751s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 2.0925471782684326s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.8307127952575684s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.768439769744873s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.738086462020874s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.307729959487915s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 3.096993923187256s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 61.90891242027283s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.17076420783996582s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.1976792812347412s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.17271995544433594s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.22043848037719727s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0012042522430419922s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0014002323150634766s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.1826035976409912s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.40791702270508s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2787802219390869s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.5510754585266113s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.2680728435516357s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.10825061798096s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.0021772384643554688s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.3722190856933594s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.1652820110321045s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.97002124786377s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.4835243225097656s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.021111488342285156s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.1682510375976562e-05s
INFO | --- Analysis for sztaki-lod took 506.39931750297546s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 9.322166442871094e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.3004791736602783s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.02288055419921875s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.221366882324219e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 9.775161743164062e-06s
INFO | --- Analysis for t4gm-info took 3.06075119972229s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.315376281738281e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.2918868064880371s
Reputation | Calculation of the PageRank for tags2con delicious took 0.023021459579467773s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.363059997558594e-05s
Believability | Calculation of trust value for tags2con delicious took 1.2636184692382812e-05s
INFO | --- Analysis for tags2con-delicious took 49.87696576118469s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.6557824611664s
Availability | VoID file availability check for Taiwan geographic names took 0.00080108642578125s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.336702823638916s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.021221399307250977s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.198883056640625e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.1444091796875e-05s
INFO | --- Analysis for taiwan-geographic-names took 667.7502892017365s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 5.173683166503906e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.27994847297668457s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.021973371505737305s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.322166442871094e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.3589859008789062e-05s
INFO | --- Analysis for talis-openlibrary took 4.188984155654907s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.8972523212432861s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.31273341178894043s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.02096843719482422s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.0001277923583984375s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.1444091796875e-05s
INFO | --- Analysis for taxonconcept took 23.0599946975708s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 9.131431579589844e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.27316761016845703s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.021074295043945312s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.416175842285156e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.4781951904296875e-05s
INFO | --- Analysis for taxonconcept-assets took 3.108614683151245s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 5.745887756347656e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2792026996612549s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.021732568740844727s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 6.747245788574219e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.3828277587890625e-05s
INFO | --- Analysis for taxonconcept-occurences took 2.985941171646118s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 21.31075692176819s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.32347798347473145s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.02079486846923828s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 5.14984130859375e-05s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.2636184692382812e-05s
INFO | --- Analysis for taxref-ld took 75.33999013900757s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 263.12062430381775s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.34189295768737793s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02152085304260254s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 2.288818359375e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.000982522964477539s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.744529724121094e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.4781951904296875e-05s
INFO | --- Analysis for tcga took 541.5739426612854s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.37947583198547363s
Availability | VoID file availability check for TCGA Roadmap took 0.0009353160858154297s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.2978694438934326s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02143383026123047s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.534027099609375e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.1205673217773438e-05s
INFO | --- Analysis for tcga-roadmap took 6.119824171066284s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.134253740310669s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3576529026031494s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.0209195613861084s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010919570922851562s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for tcmgenedit_dataset took 137.7281789779663s
Availability | SPARQL endpoint availability check for TDS took 4.410743713378906e-05s
Availability | VoID file availability check for TDS took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for TDS took 0.28867459297180176s
Reputation | Calculation of the PageRank for TDS took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for TDS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for TDS took 4.291534423828125e-05s
Believability | Calculation of trust value for TDS took 3.814697265625e-05s
INFO | --- Analysis for tds took 5.048515796661377s
Availability | SPARQL endpoint availability check for TEKORD took 8.96453857421875e-05s
Availability | VoID file availability check for TEKORD took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for TEKORD took 0.3142225742340088s
Reputation | Calculation of the PageRank for TEKORD took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.744529724121094e-05s
Believability | Calculation of trust value for TEKORD took 1.2159347534179688e-05s
INFO | --- Analysis for tekord took 5.516488075256348s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.4357144832611084s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.324826717376709s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00011229515075683594s
Believability | Calculation of trust value for Telegraphis Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for telegraphis took 8.881636619567871s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 9.202957153320312e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.3009185791015625s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.02115154266357422s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.700920104980469e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.2159347534179688e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 14.222532510757446s
Availability | SPARQL endpoint availability check for Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Ontology took 0.0007631778717041016s
Completeness | Calculation of interlinking completeness for Ontology took 0.29949259757995605s
Reputation | Calculation of the PageRank for Ontology took 0.021020174026489258s
Interlinking | Calculation of Degree of Connection for Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Terrorist_attack took 3.3315165042877197s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 0.0001659393310546875s
Availability | VoID file availability check for Terrorist Attack1 took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.31061553955078125s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.170967102050781e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.0013580322265625e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 2.729651927947998s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.38690185546875e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.27548718452453613s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.021355628967285156s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 2.9087066650390625e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.2636184692382812e-05s
INFO | --- Analysis for Tesla_Deaths took 4.281377553939819s
Availability | SPARQL endpoint availability check for test took 0.00011444091796875s
Availability | VoID file availability check for test took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for test took 0.3053450584411621s
Reputation | Calculation of the PageRank for test took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for test took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for test took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for test took 3.3855438232421875e-05s
Believability | Calculation of trust value for test took 1.049041748046875e-05s
INFO | --- Analysis for test took 2.7489442825317383s
Availability | SPARQL endpoint availability check for Test took 9.131431579589844e-05s
Availability | VoID file availability check for Test took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Test took 0.3034694194793701s
Reputation | Calculation of the PageRank for Test took 0.021327972412109375s
Interlinking | Calculation of Degree of Connection for Test took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Test took 2.8848648071289062e-05s
Believability | Calculation of trust value for Test took 9.775161743164062e-06s
INFO | --- Analysis for Test took 2.6115458011627197s
Availability | SPARQL endpoint availability check for test-svu took 20.195385456085205s
Availability | VoID file availability check for test-svu took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for test-svu took 0.31389546394348145s
Reputation | Calculation of the PageRank for test-svu took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for test-svu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.24249267578125e-05s
Believability | Calculation of trust value for test-svu took 6.4373016357421875e-06s
INFO | --- Analysis for test-svu took 52.83541250228882s
Availability | SPARQL endpoint availability check for Test took 4.363059997558594e-05s
Availability | VoID file availability check for Test took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Test took 0.30435943603515625s
Reputation | Calculation of the PageRank for Test took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for Test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Test took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Test took 3.552436828613281e-05s
Believability | Calculation of trust value for Test took 1.0728836059570312e-05s
INFO | --- Analysis for Test_ took 2.7464711666107178s
Availability | SPARQL endpoint availability check for xxxxx took 260.5814199447632s
Availability | VoID file availability check for xxxxx took 0.0009348392486572266s
Completeness | Calculation of interlinking completeness for xxxxx took 0.4249083995819092s
Reputation | Calculation of the PageRank for xxxxx took 0.021281003952026367s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for xxxxx took 6.842613220214844e-05s
Believability | Calculation of trust value for xxxxx took 1.3113021850585938e-05s
INFO | --- Analysis for testee took 795.6618399620056s
Availability | SPARQL endpoint availability check for tharawat magazine took 9.250640869140625e-05s
Availability | VoID file availability check for tharawat magazine took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.3188021183013916s
Reputation | Calculation of the PageRank for tharawat magazine took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00011014938354492188s
Believability | Calculation of trust value for tharawat magazine took 1.0728836059570312e-05s
INFO | --- Analysis for tharawat-magazine-com took 3.408189296722412s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.5032885074615479s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.2902705669403076s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.022633790969848633s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.24249267578125e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.1682510375976562e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 7.9387993812561035s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.3024487495422363s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007696151733398438s
Extra | Recovery of all triples for The European Library Open Dataset took 6.981509447097778s
Performance | Total latancy measurement for The European Library Open Dataset took 16.006349086761475s
Amount of data | Number of triples check for The European Library Open Dataset took 63.82080268859863s
Interoperability | New terms check for The European Library Open Dataset took 59.38397026062012s
Versatility | Languages check for The European Library Open Dataset took 3.1972172260284424s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.196479320526123s
Interpretability | RDF structures check for The European Library Open Dataset took 3.2110586166381836s
Versatility | Serialization formats check for The European Library Open Dataset took 3.1981685161590576s
Availability | RDF dump link check for The European Library Open Dataset took 3.1958160400390625s
License | MR license check for The European Library Open Dataset took 3.211642026901245s
License | HR license check for The European Library Open Dataset took 3.1957144737243652s
Amount of data | Number of property check for The European Library Open Dataset took 3.2042548656463623s
Understandability | Number of label check for The European Library Open Dataset took 3.7375283241271973s
Understandability | URI regex check for The European Library Open Dataset took 6.395946979522705s
Understandability | Vocabs check for The European Library Open Dataset took 3.20542573928833s
Verifiability | Authors check for The European Library Open Dataset took 3.1980018615722656s
Verifiability | Publishers check for The European Library Open Dataset took 3.1970372200012207s
Performance | Throughput check for The European Library Open Dataset took 31.999032974243164s
Amount of data | Check the number of entities for The European Library Open Dataset took 4.839897155761719e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.208287239074707s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.311598300933838s
Interlinking | skos check for The European Library Open Dataset took 3.263427495956421s
Interlinking | skos check for The European Library Open Dataset took 3.2849392890930176s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.1995909214019775s
Currency | Creation date check for The European Library Open Dataset took 6.398612022399902s
Currency | Modification date check for The European Library Open Dataset took 6.427602052688599s
Rep.Conc. | URIs length for The European Library Open Dataset took 123.16214513778687s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 2.015302896499634s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.5355331897735596s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02655816078186035s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02921748161315918s
Consistency | Disjoint class check for The European Library Open Dataset took 3.2202069759368896s
Consistency | Check Misplaced properties for The European Library Open Dataset took 66.58056092262268s
Consistency | Misplaced classes for The European Library Open Dataset took 3.3050262928009033s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.876100540161133s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.2931294441223145s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 65.68862795829773s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.033776044845581055s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.183340072631836s
Security | Sign check for The European Library Open Dataset took 3.20807147026062s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 11.619635105133057s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.5743725299835205s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.021574974060058594s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.628036499023438e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.1444091796875e-05s
INFO | --- Analysis for the-european-library-open-dataset took 874.0943455696106s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.04064869880676s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.3835322856903076s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00011968612670898438s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for the-eurostat-linked-data took 242.97055673599243s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 9.441375732421875e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.3076162338256836s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02164292335510254s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.62939453125e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.3589859008789062e-05s
INFO | --- Analysis for the-living-lod-cloud took 43.85438370704651s
Availability | SPARQL endpoint availability check for The View From took 20.039709329605103s
Availability | VoID file availability check for The View From took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for The View From took 0.2906479835510254s
Reputation | Calculation of the PageRank for The View From took 0.020846843719482422s
Interlinking | Calculation of Degree of Connection for The View From took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for The View From took 8.726119995117188e-05s
Believability | Calculation of trust value for The View From took 1.2874603271484375e-05s
INFO | --- Analysis for the-view-from took 62.83473229408264s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.673405408859253s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0008330345153808594s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2783350944519043s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 7.963180541992188e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 8.58306884765625e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.41258192062378s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.19451928138733s
Availability | VoID file availability check for Open data of Uzbekistan took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.39484190940856934s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.021515846252441406s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.314018249511719e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.0013580322265625e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.6684467792511s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.315376281738281e-05s
Availability | VoID file availability check for The Content Wrangler took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.3036472797393799s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.027840852737426758s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0015599727630615234s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00021314620971679688s
Believability | Calculation of trust value for The Content Wrangler took 1.1920928955078125e-05s
INFO | --- Analysis for thecontentwrangler-com took 3.222432851791382s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 9.059906005859375e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.3093903064727783s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.0216219425201416s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.314018249511719e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.3113021850585938e-05s
INFO | --- Analysis for thesaurus-datenwissen took 2.7893552780151367s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.6241316795349121s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.2997281551361084s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.891654968261719e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 2.5987625122070312e-05s
INFO | --- Analysis for thesaurus-w took 4.241075277328491s
Availability | SPARQL endpoint availability check for theses.fr took 4.291534423828125e-05s
Availability | VoID file availability check for theses.fr took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for theses.fr took 0.27055835723876953s
Reputation | Calculation of the PageRank for theses.fr took 0.021067380905151367s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.054473876953125e-05s
Believability | Calculation of trust value for theses.fr took 6.198883056640625e-06s
INFO | --- Analysis for thesesfr took 4.340623378753662s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 8.535385131835938e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.31531715393066406s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.4809112548828125e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 5.7220458984375e-06s
INFO | --- Analysis for Thinkphile took 2.564723253250122s
Availability | SPARQL endpoint availability check for ThIST took 266.83279633522034s
Availability | VoID file availability check for ThIST took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for ThIST took 0.30118870735168457s
Reputation | Calculation of the PageRank for ThIST took 0.021143436431884766s
Interlinking | Calculation of Degree of Connection for ThIST took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0008544921875s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.96453857421875e-05s
Believability | Calculation of trust value for ThIST took 1.0013580322265625e-05s
INFO | --- Analysis for thist took 567.3024852275848s
Availability | SPARQL endpoint availability check for TIP took 40.037678241729736s
Availability | VoID file availability check for TIP took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for TIP took 0.37142395973205566s
Reputation | Calculation of the PageRank for TIP took 0.02113962173461914s
Interlinking | Calculation of Degree of Connection for TIP took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011515617370605469s
Believability | Calculation of trust value for TIP took 5.0067901611328125e-06s
INFO | --- Analysis for tip took 102.91304802894592s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 9.298324584960938e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.3290822505950928s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.022587299346923828s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.147125244140625e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.0251998901367188e-05s
INFO | --- Analysis for TOPMODEL took 24.03294277191162s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.454855442047119s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.2824246883392334s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.0223085880279541s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 4.57763671875e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.0013580322265625e-05s
INFO | --- Analysis for TP-data took 7.533799648284912s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.35106921195983887s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.34009480476379395s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.7206878662109375e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for traditional-korean-medicine took 3.780935525894165s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.25170397758483887s
Availability | VoID file availability check for Traffic Scotland took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.2862398624420166s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.814697265625e-05s
Believability | Calculation of trust value for Traffic Scotland took 9.059906005859375e-06s
INFO | --- Analysis for traffic-scotland took 3.0055429935455322s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.1120598316192627s
Availability | VoID file availability check for Transparency International Linked Data took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.3070697784423828s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.021990299224853516s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00011777877807617188s
Believability | Calculation of trust value for Transparency International Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for transparency-linked-data took 2.821054458618164s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.6741738319396973s
Availability | VoID file availability check for transport.data.gov.uk took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2769911289215088s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.021062135696411133s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.632110595703125e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 5.9604644775390625e-06s
INFO | --- Analysis for transport-data-gov-uk took 4.179994821548462s
Availability | SPARQL endpoint availability check for Trelios took 8.606910705566406e-05s
Availability | VoID file availability check for Trelios took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Trelios took 0.2899785041809082s
Reputation | Calculation of the PageRank for Trelios took 0.021574974060058594s
Interlinking | Calculation of Degree of Connection for Trelios took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.3828277587890625e-05s
Believability | Calculation of trust value for Trelios took 1.3828277587890625e-05s
INFO | --- Analysis for Trelios took 2.7074286937713623s
Availability | SPARQL endpoint availability check for Twarql took 10.664594173431396s
Availability | VoID file availability check for Twarql took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Twarql took 0.33142900466918945s
Reputation | Calculation of the PageRank for Twarql took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for Twarql took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Twarql took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Twarql took 7.009506225585938e-05s
Believability | Calculation of trust value for Twarql took 1.4066696166992188e-05s
INFO | --- Analysis for twarql took 13.377340316772461s
Availability | SPARQL endpoint availability check for TWC Data-gov took 0.00010848045349121094s
Availability | VoID file availability check for TWC Data-gov took 0.0007953643798828125s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.2746729850769043s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.1948089599609375e-05s
Believability | Calculation of trust value for TWC Data-gov took 9.298324584960938e-06s
INFO | --- Analysis for twc-data-gov took 13.111795425415039s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.14785242080688477s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007581710815429688s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.3381679058074951s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.02107548713684082s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.790855407714844e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 9.5367431640625e-06s
INFO | --- Analysis for twc-healthdata took 14.647804737091064s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.101284503936768s
Availability | VoID file availability check for Instance Hub (all) took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.2788875102996826s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.021146535873413086s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 8.153915405273438e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.049041748046875e-05s
INFO | --- Analysis for twc-hub took 78.97010135650635s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.13668441772460938s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.3676316738128662s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.021255970001220703s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0010190010070800781s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.0001277923583984375s
Believability | Calculation of trust value for IEEE VIS Source Data took 8.344650268554688e-06s
INFO | --- Analysis for twc-ieeevis took 105.38120651245117s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 8.797645568847656e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.3278052806854248s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02121710777282715s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.250640869140625e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 9.5367431640625e-06s
INFO | --- Analysis for twc-logd took 2.875612735748291s
Availability | SPARQL endpoint availability check for twc-opendap took 0.13361120223999023s
Availability | VoID file availability check for twc-opendap took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.33658766746520996s
Reputation | Calculation of the PageRank for twc-opendap took 0.021105527877807617s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 7.748603820800781e-05s
Believability | Calculation of trust value for twc-opendap took 1.1682510375976562e-05s
INFO | --- Analysis for twc-opendap took 51.37396717071533s
Availability | SPARQL endpoint availability check for typepad took 4.4345855712890625e-05s
Availability | VoID file availability check for typepad took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for typepad took 0.2883152961730957s
Reputation | Calculation of the PageRank for typepad took 0.021589279174804688s
Interlinking | Calculation of Degree of Connection for typepad took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for typepad took 0.0009887218475341797s
Interlinking | Calculation of Clustering coefficient for typepad took 6.651878356933594e-05s
Believability | Calculation of trust value for typepad took 1.33514404296875e-05s
INFO | --- Analysis for typepad took 3.285926103591919s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.8921256065368652s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.28887009620666504s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.022742271423339844s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.2438507080078125e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.049041748046875e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 4.9347240924835205s
Availability | SPARQL endpoint availability check for Uberblic.org took 5.146739482879639s
Availability | VoID file availability check for Uberblic.org took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.33204030990600586s
Reputation | Calculation of the PageRank for Uberblic.org took 0.02184462547302246s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010752677917480469s
Believability | Calculation of trust value for Uberblic.org took 1.0967254638671875e-05s
INFO | --- Analysis for uberblic took 12.76915955543518s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6953916549682617s
Availability | VoID file availability check for UDante in LiLa took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.28876471519470215s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.021199464797973633s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.029273986816406e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for UDante took 4.614274978637695s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.9772200584411621s
Availability | VoID file availability check for Unified Foundational Ontology took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.28772568702697754s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.022108078002929688s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for ufo took 4.995701551437378s
Availability | SPARQL endpoint availability check for Uganda Disasters took 8.988380432128906e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.3096446990966797s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.02238607406616211s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.935264587402344e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.3828277587890625e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.702815532684326s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.059095144271850586s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.28551626205444336s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020934104919433594s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00011348724365234375s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for uis-linked-data took 2.843385696411133s
Availability | SPARQL endpoint availability check for UK Legislation took 8.893013000488281e-05s
Availability | VoID file availability check for UK Legislation took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.27907419204711914s
Reputation | Calculation of the PageRank for UK Legislation took 0.021182775497436523s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.869171142578125e-05s
Believability | Calculation of trust value for UK Legislation took 7.867813110351562e-06s
INFO | --- Analysis for uk-legislation-api took 3.7101242542266846s
Availability | SPARQL endpoint availability check for UK Postcodes took 8.845329284667969e-05s
Availability | VoID file availability check for UK Postcodes took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.32445311546325684s
Reputation | Calculation of the PageRank for UK Postcodes took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 6.198883056640625e-05s
Believability | Calculation of trust value for UK Postcodes took 1.0013580322265625e-05s
INFO | --- Analysis for uk-postcodes took 22.72676920890808s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.410743713378906e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.30437779426574707s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.021846771240234375s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0001227855682373047s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.0251998901367188e-05s
INFO | --- Analysis for umbel took 7.423144340515137s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 0.00013065338134765625s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.31180691719055176s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.02112269401550293s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.5299530029296875e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 9.775161743164062e-06s
INFO | --- Analysis for umthes took 3.7993323802948s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.7172276973724365s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0007557868957519531s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.2752668857574463s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.24249267578125e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 8.821487426757812e-06s
INFO | --- Analysis for un-hazardous-numbers took 10.32761836051941s
Availability | SPARQL endpoint availability check for UniProt took 3.125173807144165s
Availability | VoID file availability check for UniProt took 0.0007531642913818359s
Extra | Recovery of all triples for UniProt took 18.898885011672974s
Performance | Total latancy measurement for UniProt took 6.457692384719849s
Amount of data | Number of triples check for UniProt took 0.6139848232269287s
Interoperability | New terms check for UniProt took 1.659330129623413s
Versatility | Languages check for UniProt took 1.5477018356323242s
Interpretability | Number of blank nodes check for UniProt took 3.15240478515625s
Interpretability | RDF structures check for UniProt took 1.7423210144042969s
Versatility | Serialization formats check for UniProt took 2.403151750564575s
Availability | RDF dump link check for UniProt took 0.3294193744659424s
License | MR license check for UniProt took 1.287750482559204s
License | HR license check for UniProt took 300.10180830955505s
Amount of data | Number of property check for UniProt took 0.09517240524291992s
Understandability | Number of label check for UniProt took 44.548837184906006s
Understandability | URI regex check for UniProt took 0.9262938499450684s
Understandability | Vocabs check for UniProt took 0.8100922107696533s
Verifiability | Authors check for UniProt took 1.7467432022094727s
Verifiability | Publishers check for UniProt took 1.3802218437194824s
Performance | Throughput check for UniProt took 33.52795433998108s
Amount of data | Check the number of entities for UniProt took 7.367134094238281e-05s
Verifiability | Contribs. check for UniProt took 0.6966137886047363s
Interlinking | sameAs chians check for UniProt took 0.485567569732666s
Interlinking | skos check for UniProt took 1.291898488998413s
Interlinking | skos check for UniProt took 0.08659076690673828s
Timeliness | dataset update frequency check for UniProt took 1.309553623199463s
Currency | Creation date check for UniProt took 1.7959139347076416s
Currency | Modification date check for UniProt took 1.6078500747680664s
Rep.Conc. | URIs length for UniProt took 117.78743505477905s
Interoperability | New vocabularies check for UniProt took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.36849236488342285s
Accuracy | Check Functional Property for UniProt took 0.3585543632507324s
Accuracy | Check Inverse Functional Property for UniProt took 0.35050272941589355s
Accuracy | Check Empty annotation labels for UniProt took 17.656588792800903s
Accuracy | Check White space in annotation for UniProt took 2.5184388160705566s
Accuracy | Check Datatype consistency for UniProt took 7.211385250091553s
Consistency | Disjoint class check for UniProt took 0.3340277671813965s
Consistency | Check Misplaced properties for UniProt took 2.024188280105591s
Consistency | Check Ontology hijacking for UniProt took 7.589662790298462s
Consistency | Check Invalid usage of undefined classes for UniProt took 18693.144662857056s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.9049749374389648s
Conciseness | Check Extensional conciseness for UniProt took 2.7492165565490723s
Conciseness | Check Intensional conciseness for UniProt took 0.7540602684020996s
Security | Sign check for UniProt took 1.095506191253662s
Availability | Check URIs Dereferenciability for UniProt took 4.85467529296875s
Completeness | Calculation of interlinking completeness for UniProt took 0.852837324142456s
Reputation | Calculation of the PageRank for UniProt took 0.021370887756347656s
Interlinking | Calculation of Degree of Connection for UniProt took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProt took 1.0251998901367188e-05s
INFO | --- Analysis for UniProt took 19708.108249664307s
Availability | SPARQL endpoint availability check for UniProt took 3.020811080932617s
Availability | VoID file availability check for UniProt took 0.00063323974609375s
Extra | Recovery of all triples for UniProt took 17.165188789367676s
Performance | Total latancy measurement for UniProt took 6.540045499801636s
Amount of data | Number of triples check for UniProt took 0.6336536407470703s
Versatility | Languages check for UniProt took 1.661301612854004s
Interpretability | Number of blank nodes check for UniProt took 2.9484200477600098s
Security | Check HTTPS for UniProt took 3.3874306678771973s
Interpretability | RDF structures check for UniProt took 0.17619538307189941s
Versatility | Serialization formats check for UniProt took 0.17525744438171387s
Availability | RDF dump link check for UniProt took 0.17722558975219727s
License | MR license check for UniProt took 0.16701316833496094s
License | HR license check for UniProt took 0.16049432754516602s
Amount of data | Number of property check for UniProt took 0.17138004302978516s
Understandability | Number of label check for UniProt took 0.18680191040039062s
Understandability | URI regex check for UniProt took 0.3313565254211426s
Understandability | Vocabs check for UniProt took 0.16246604919433594s
Verifiability | Authors check for UniProt took 0.18071770668029785s
Verifiability | Publishers check for UniProt took 0.17082881927490234s
Performance | Throughput check for UniProt took 32.14930534362793s
Amount of data | Check the number of entities for UniProt took 0.00018906593322753906s
Verifiability | Contribs. check for UniProt took 0.21328377723693848s
Interlinking | sameAs chians check for UniProt took 0.16363167762756348s
Interlinking | skos check for UniProt took 0.16123533248901367s
Interlinking | skos check for UniProt took 0.13842535018920898s
Timeliness | dataset update frequency check for UniProt took 0.16634917259216309s
Currency | Creation date check for UniProt took 0.3515491485595703s
Currency | Modification date check for UniProt took 0.33531951904296875s
Rep.Conc. | URIs length for UniProt took 114.33138585090637s
Interoperability | New vocabularies check for UniProt took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.17119359970092773s
Accuracy | Check Datatype consistency for UniProt took 7.1787660121917725s
Consistency | Disjoint class check for UniProt took 0.15486383438110352s
Consistency | Check Ontology hijacking for UniProt took 0.18177533149719238s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.859525442123413s
Conciseness | Check Extensional conciseness for UniProt took 2.7614693641662598s
Security | Sign check for UniProt took 0.16782140731811523s
Availability | Check URIs Dereferenciability for UniProt took 4.7925567626953125s
Completeness | Calculation of interlinking completeness for UniProt took 0.41350221633911133s
Reputation | Calculation of the PageRank for UniProt took 0.021469831466674805s
Interlinking | Calculation of Degree of Connection for UniProt took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for UniProt took 7.152557373046875e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.430511474609375e-06s
Believability | Calculation of trust value for UniProt took 1.239776611328125e-05s
INFO | --- Analysis for uniprot took 743.332777261734s
Availability | SPARQL endpoint availability check for uniprot-metadata took 9.965896606445312e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.2869679927825928s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020467758178710938s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.270408630371094e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.2874603271484375e-05s
INFO | --- Analysis for uniprot-metadata took 4.022632122039795s
Availability | SPARQL endpoint availability check for UniProtKB took 3.4536314010620117s
Availability | VoID file availability check for UniProtKB took 0.0005524158477783203s
Extra | Recovery of all triples for UniProtKB took 17.44196629524231s
Performance | Total latancy measurement for UniProtKB took 7.008594989776611s
Amount of data | Number of triples check for UniProtKB took 0.4696180820465088s
Interoperability | New terms check for UniProtKB took 1.6619162559509277s
Versatility | Languages check for UniProtKB took 1.5590088367462158s
Interpretability | Number of blank nodes check for UniProtKB took 3.157186985015869s
Interpretability | RDF structures check for UniProtKB took 1.628326416015625s
Versatility | Serialization formats check for UniProtKB took 2.3125369548797607s
Availability | RDF dump link check for UniProtKB took 0.3346290588378906s
License | MR license check for UniProtKB took 1.2229976654052734s
License | HR license check for UniProtKB took 300.15935754776s
Amount of data | Number of property check for UniProtKB took 0.14513540267944336s
Understandability | Number of label check for UniProtKB took 53.944488525390625s
Understandability | URI regex check for UniProtKB took 1.0280394554138184s
Understandability | Vocabs check for UniProtKB took 1.005011796951294s
Verifiability | Authors check for UniProtKB took 1.62506103515625s
Verifiability | Publishers check for UniProtKB took 1.2638585567474365s
Performance | Throughput check for UniProtKB took 36.01311182975769s
Amount of data | Check the number of entities for UniProtKB took 6.961822509765625e-05s
Verifiability | Contribs. check for UniProtKB took 0.7161464691162109s
Interlinking | sameAs chians check for UniProtKB took 0.5281314849853516s
Interlinking | skos check for UniProtKB took 1.1717901229858398s
Interlinking | skos check for UniProtKB took 0.07622647285461426s
Timeliness | dataset update frequency check for UniProtKB took 1.3178837299346924s
Currency | Creation date check for UniProtKB took 1.6715478897094727s
Currency | Modification date check for UniProtKB took 1.614732265472412s
Rep.Conc. | URIs length for UniProtKB took 121.27224969863892s
Interoperability | New vocabularies check for UniProtKB took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.5055575370788574s
Accuracy | Check Functional Property for UniProtKB took 0.46442317962646484s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.3467743396759033s
Accuracy | Check Empty annotation labels for UniProtKB took 9.849843263626099s
Accuracy | Check White space in annotation for UniProtKB took 2.5205867290496826s
Accuracy | Check Datatype consistency for UniProtKB took 7.243499517440796s
Consistency | Disjoint class check for UniProtKB took 0.46831393241882324s
Consistency | Check Misplaced properties for UniProtKB took 1.7531077861785889s
Consistency | Check Ontology hijacking for UniProtKB took 8.64108419418335s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 18865.047689437866s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 1.843874216079712s
Conciseness | Check Extensional conciseness for UniProtKB took 2.7568209171295166s
Conciseness | Check Intensional conciseness for UniProtKB took 0.8192219734191895s
Security | Sign check for UniProtKB took 1.0911812782287598s
Availability | Check URIs Dereferenciability for UniProtKB took 4.6447227001190186s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.8979451656341553s
Reputation | Calculation of the PageRank for UniProtKB took 0.021688461303710938s
Interlinking | Calculation of Degree of Connection for UniProtKB took 0.0003235340118408203s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.384185791015625e-06s
Believability | Calculation of trust value for UniProtKB took 1.1205673217773438e-05s
INFO | --- Analysis for uniprotkb took 19891.222019910812s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 9.274482727050781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0007770061492919922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.3083045482635498s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.02085089683532715s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.647701263427734s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.28171873092651367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020819902420043945s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 3.9408204555511475s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.7206878662109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.330888032913208s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.0221097469329834s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.378973722457886s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2840237617492676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.457131147384644s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.25984716415405273s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.288922548294067s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.2809715270996094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.271027565002441s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0004050731658935547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.3177366256713867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.196788787841797s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.27040576934814453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.295578241348267s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.2879953384399414s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.388755798339844s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 8.749961853027344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.30847644805908203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.327713012695312s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 8.96453857421875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.30987048149108887s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 5.0067901611328125e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.240368843078613s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 9.703636169433594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.3036046028137207s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.021592378616333008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.221224308013916s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 8.893013000488281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2761497497558594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.022289037704467773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.099194288253784s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0007545948028564453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.29538917541503906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.021409034729003906s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.451741933822632s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 9.34600830078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.28835511207580566s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.223567724227905s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0007495880126953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.27456045150756836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 5.4836273193359375e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.399397373199463s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 8.916854858398438e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.4245622158050537s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.022396087646484375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.409651517868042s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 0.00011539459228515625s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0008046627044677734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.2888362407684326s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.280956268310547s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.3118312358856201s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.02193450927734375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.617323398590088s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.3060469627380371s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.137220144271851s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0008025169372558594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.30240654945373535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.02258610725402832s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.222485303878784s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 9.894371032714844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2882976531982422s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.021416902542114258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.405777931213379s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 8.940696716308594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.30610084533691406s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.380887985229492s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0002048015594482422s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.3059680461883545s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.929661750793457s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 9.298324584960938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0008327960968017578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.2905302047729492s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 4.1469244956970215s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 0.00010728836059570312s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.3066129684448242s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.02112269401550293s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 4.033932447433472s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.331545352935791s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.0207216739654541s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 4.02935266494751s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0007822513580322266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.2904047966003418s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.528772115707397s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.2970261573791504s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.021036148071289062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.66649341583252s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.2897017002105713s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.02102041244506836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 4.135077714920044s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.30905938148498535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.328641176223755s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 8.916854858398438e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.32170677185058594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.0489501953125s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 8.821487426757812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.30723094940185547s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.021468162536621094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0010042190551757812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 5.1021575927734375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.425967931747437s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 9.131431579589844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0008208751678466797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.29094505310058594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.02085256576538086s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.547165155410767s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0007839202880859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.2851555347442627s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.024801254272460938s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0012004375457763672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 5.4836273193359375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 3.997149705886841s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.28035879135131836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.352301359176636s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.29119348526000977s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.02181410789489746s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 4.142352819442749s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 0.00016832351684570312s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.29544711112976074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.308846950531006s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 5.14984130859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0008289813995361328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.31148242950439453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.021304845809936523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 5.6743621826171875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.34876012802124s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 9.131431579589844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0007562637329101562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.29393649101257324s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.021215200424194336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.744529724121094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.364482641220093s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.000835418701171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.2773561477661133s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.02173447608947754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.22184419631958s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.00012636184692382812s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.3106095790863037s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.440838098526001s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 8.96453857421875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.28847742080688477s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.021154165267944336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-persian took 3.929748058319092s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0008158683776855469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.3014845848083496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.021591901779174805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.385702848434448s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 9.059906005859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0008676052093505859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.29143190383911133s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.021217823028564453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0009276866912841797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.863739013671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 13.019354581832886s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2916405200958252s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.02092123031616211s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.241286754608154s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.349747896194458s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.022072792053222656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.5213942527771s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0008571147918701172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.28345608711242676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.489346027374268s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 0.000110626220703125s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0009198188781738281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.29224419593811035s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020932674407958984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.561612606048584s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.3025221824645996s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02280116081237793s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 4.120862722396851s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.744529724121094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0008041858673095703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.3019862174987793s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.021803855895996094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.641868352890015s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.649162292480469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.3131070137023926s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 5.0067901611328125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.281904697418213s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0007581710815429688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.2863316535949707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.0211639404296875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.431914806365967s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 9.083747863769531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.27841949462890625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020875930786132812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.22996711730957s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.3015162944793701s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.021632671356201172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.519673347473145s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 9.298324584960938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.34356164932250977s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.02107977867126465s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.214775562286377s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 9.1552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.31265854835510254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.020907878875732422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0010395050048828125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 5.0067901611328125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 4.127750873565674s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 9.012222290039062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.31664371490478516s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.02256917953491211s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 4.018454551696777s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.29765963554382324s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.494104862213135s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 6.270408630371094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.2923269271850586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020866870880126953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.278932809829712s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 9.751319885253906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0007450580596923828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.28916382789611816s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020644187927246094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.5735626220703125e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.502808570861816s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.9114227294921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.30312514305114746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.02145552635192871s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.334702253341675s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 8.916854858398438e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2907443046569824s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.020745277404785156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.540893793106079s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.3164639472961426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.02229166030883789s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.462982416152954s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 9.274482727050781e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.28017544746398926s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.02247786521911621s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.699562072753906e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.3113021850585938e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.962529420852661s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.2438507080078125e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2942941188812256s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.6743621826171875e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.3589859008789062e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 3.3130033016204834s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 9.322166442871094e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.283158540725708s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.02095341682434082s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.6716461181640625e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.4781951904296875e-05s
INFO | --- Analysis for university-sussex-reading-lists took 3.0681540966033936s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 9.000218868255615s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.3094189167022705s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.022249221801757812s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.486343383789062e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.4066696166992188e-05s
INFO | --- Analysis for unodc took 24.669721841812134s
Availability | SPARQL endpoint availability check for Super Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Super Ontology took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.31061434745788574s
Reputation | Calculation of the PageRank for Super Ontology took 0.02198314666748047s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 8.225440979003906e-05s
Believability | Calculation of trust value for Super Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for upper-ontology took 3.7810635566711426s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.8275749683380127s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.28063011169433594s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.02102518081665039s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0009889602661132812s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 4.363059997558594e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.430511474609375e-05s
INFO | --- Analysis for Upper_Ontology took 5.364319086074829s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 4.506111145019531e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.3039565086364746s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 2.7418136596679688e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.3589859008789062e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.7178709506988525s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.722459077835083s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0005080699920654297s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 104.25015044212341s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 0.9891364574432373s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.325502634048462s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.42143964767456s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.2122151851654s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.123682975769043s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.34337472915649414s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 8.338752269744873s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.40192341804504395s
License | MR license check for Urban Atlas dataset @PSNC took 0.9056127071380615s
License | HR license check for Urban Atlas dataset @PSNC took 245.05201363563538s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.23259258270263672s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 3.3844034671783447s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 1.291771650314331s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.6907804012298584s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.22481608390808105s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.25467872619628906s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.284650564193726s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 6.389617919921875e-05s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.19705629348754883s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.22537851333618164s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.5282566547393799s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.4141669273376465s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 8.60883617401123s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.526151180267334s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.2872636318206787s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 143.98975491523743s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.21452641487121582s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.515932559967041s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.4714188575744629s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 35.4157190322876s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.6761233806610107s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.623319149017334s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.18465280532836914s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 87.05242919921875s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.182420492172241s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 34.365802526474s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.3300421237945557s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 87.80783677101135s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.790245294570923s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.5284759998321533s
Security | Sign check for Urban Atlas dataset @PSNC took 1.6587119102478027s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 16.67943048477173s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.516420841217041s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.021555662155151367s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 3.24249267578125e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for Urban_Atlas_Dataset took 2202.69046831131s
Availability | SPARQL endpoint availability check for URIBurner took 1.020493745803833s
Availability | VoID file availability check for URIBurner took 0.0006306171417236328s
Extra | Recovery of all triples for URIBurner took 120.94630789756775s
Performance | Total latancy measurement for URIBurner took 2.7517964839935303s
Amount of data | Number of triples check for URIBurner took 3.464158296585083s
Interoperability | New terms check for URIBurner took 37.57037305831909s
Versatility | Languages check for URIBurner took 121.58669328689575s
Interpretability | Number of blank nodes check for URIBurner took 1.8889141082763672s
Security | Check HTTPS for URIBurner took 0.8786163330078125s
Interpretability | RDF structures check for URIBurner took 0.8582768440246582s
Versatility | Serialization formats check for URIBurner took 6.209222316741943s
Availability | RDF dump link check for URIBurner took 45.37399959564209s
License | MR license check for URIBurner took 0.8136789798736572s
License | HR license check for URIBurner took 123.30389451980591s
Amount of data | Number of property check for URIBurner took 0.7828938961029053s
Understandability | Number of label check for URIBurner took 3.107248067855835s
Understandability | URI regex check for URIBurner took 1.2621896266937256s
Understandability | Vocabs check for URIBurner took 0.6301445960998535s
Verifiability | Authors check for URIBurner took 0.7423787117004395s
Verifiability | Publishers check for URIBurner took 0.6037604808807373s
Performance | Throughput check for URIBurner took 10.92263150215149s
Amount of data | Check the number of entities for URIBurner took 0.00010085105895996094s
Verifiability | Contribs. check for URIBurner took 0.5872807502746582s
Interlinking | sameAs chians check for URIBurner took 1.016277551651001s
Interlinking | skos check for URIBurner took 0.5936791896820068s
Interlinking | skos check for URIBurner took 0.5557551383972168s
Timeliness | dataset update frequency check for URIBurner took 1.0116243362426758s
Currency | Creation date check for URIBurner took 3.1829116344451904s
Currency | Modification date check for URIBurner took 0.6738290786743164s
Rep.Conc. | URIs length for URIBurner took 113.12245225906372s
Interoperability | New vocabularies check for URIBurner took 23.868095636367798s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.6565849781036377s
Accuracy | Check Functional Property for URIBurner took 0.6066937446594238s
Accuracy | Check Inverse Functional Property for URIBurner took 0.5599074363708496s
Accuracy | Check Empty annotation labels for URIBurner took 56.02510380744934s
Accuracy | Check White space in annotation for URIBurner took 0.18503522872924805s
Consistency | Disjoint class check for URIBurner took 0.5880982875823975s
Consistency | Check Misplaced properties for URIBurner took 399.10711765289307s
Consistency | Misplaced classes for URIBurner took 56.06300687789917s
Consistency | Check Ontology hijacking for URIBurner took 57.51215696334839s
Consistency | Check Invalid usage of undefined properties for URIBurner took 58.486597299575806s
Conciseness | Check Extensional conciseness for URIBurner took 0.00017833709716796875s
Conciseness | Check Intensional conciseness for URIBurner took 108.73821258544922s
Security | Sign check for URIBurner took 0.9099187850952148s
Completeness | Calculation of interlinking completeness for URIBurner took 2.1957943439483643s
Reputation | Calculation of the PageRank for URIBurner took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.560585021972656e-05s
Interoperability | Check the re-using of existing vocabs for URIBurner took 22.92728328704834s
Believability | Calculation of trust value for URIBurner took 1.1444091796875e-05s
INFO | --- Analysis for uriburner took 13715.89028429985s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.584426879882812e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.28253722190856934s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0009958744049072266s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.5299530029296875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.2159347534179688e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.849465847015381s
Availability | SPARQL endpoint availability check for Legija Stranaca took 8.916854858398438e-05s
Availability | VoID file availability check for Legija Stranaca took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.2858924865722656s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.02101898193359375s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.266334533691406e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.1682510375976562e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.781623363494873s
Availability | SPARQL endpoint availability check for Legija took 8.630752563476562e-05s
Availability | VoID file availability check for Legija took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Legija took 0.30506420135498047s
Reputation | Calculation of the PageRank for Legija took 0.02058863639831543s
Interlinking | Calculation of Degree of Connection for Legija took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Legija took 3.0279159545898438e-05s
Believability | Calculation of trust value for Legija took 1.4543533325195312e-05s
INFO | --- Analysis for Uros_Susa took 2.7094919681549072s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.5366954803466797s
Availability | VoID file availability check for USAGE review corpus took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.297435998916626s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.337860107421875e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.3589859008789062e-05s
INFO | --- Analysis for usage-review-corpus took 4.372676134109497s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 3.866645574569702s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.2887241840362549s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.000997781753540039s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 9.72747802734375e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for utpl-lod took 10.46441912651062s
Availability | SPARQL endpoint availability check for terrorist attack took 4.458427429199219e-05s
Availability | VoID file availability check for terrorist attack took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.31289148330688477s
Reputation | Calculation of the PageRank for terrorist attack took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.266334533691406e-05s
Believability | Calculation of trust value for terrorist attack took 1.0967254638671875e-05s
INFO | --- Analysis for varsha took 4.421573638916016s
Availability | SPARQL endpoint availability check for VA took 4.9114227294921875e-05s
Availability | VoID file availability check for VA took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for VA took 0.29604125022888184s
Reputation | Calculation of the PageRank for VA took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for VA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VA took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for VA took 3.170967102050781e-05s
Believability | Calculation of trust value for VA took 1.2874603271484375e-05s
INFO | --- Analysis for Vehicule_Autonome took 2.943345785140991s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.7057650089263916s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.3354768753051758s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 6.532669067382812e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.3828277587890625e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.705620050430298s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.566707372665405s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.288654088973999s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.021431446075439453s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.726119995117188e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.3113021850585938e-05s
INFO | --- Analysis for verrijktkoninkrijk took 15.55813479423523s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 8.845329284667969e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0008022785186767578s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.3081502914428711s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017881393432617188s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.3828277587890625e-05s
INFO | --- Analysis for viaf took 20.664772987365723s
Availability | SPARQL endpoint availability check for Vihar Exports took 9.226799011230469e-05s
Availability | VoID file availability check for Vihar Exports took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.320023775100708s
Reputation | Calculation of the PageRank for Vihar Exports took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.075599670410156e-05s
Believability | Calculation of trust value for Vihar Exports took 1.3589859008789062e-05s
INFO | --- Analysis for Vihar_Exports took 2.8043270111083984s
Availability | SPARQL endpoint availability check for VIVO took 9.179115295410156e-05s
Availability | VoID file availability check for VIVO took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for VIVO took 0.3004615306854248s
Reputation | Calculation of the PageRank for VIVO took 0.02121591567993164s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.176399230957031e-05s
Believability | Calculation of trust value for VIVO took 1.239776611328125e-05s
INFO | --- Analysis for vivo took 5.836299180984497s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.4345855712890625e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.2881479263305664s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.130073547363281e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.2636184692382812e-05s
INFO | --- Analysis for vivo-cornell-university took 6.225475788116455s
Availability | SPARQL endpoint availability check for VIVO Indiana took 8.797645568847656e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 1.4537403583526611s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.02050161361694336s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.106231689453125e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.3113021850585938e-05s
INFO | --- Analysis for vivo-indiana-university took 5.610603094100952s
Availability | SPARQL endpoint availability check for VIVO Ponce took 8.749961853027344e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.3047633171081543s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 4.3392181396484375e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.3113021850585938e-05s
INFO | --- Analysis for vivo-ponce took 4.357343912124634s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 9.179115295410156e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.29786181449890137s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.719329833984375e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.2874603271484375e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 3.1421890258789062s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 9.107589721679688e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.32924437522888184s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.021561622619628906s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.107589721679688e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.3113021850585938e-05s
INFO | --- Analysis for vivo-university-of-florida took 2.8765203952789307s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 9.1552734375e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.29537081718444824s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.021285295486450195s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.552436828613281e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 7.867813110351562e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 3.1667590141296387s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 9.226799011230469e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.31701087951660156s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.021058320999145508s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 4.076957702636719e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.1920928955078125e-05s
INFO | --- Analysis for vivo-wustl took 3.167168617248535s
Availability | SPARQL endpoint availability check for vivo2doi took 5.91278076171875e-05s
Availability | VoID file availability check for vivo2doi took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.31029248237609863s
Reputation | Calculation of the PageRank for vivo2doi took 0.022541522979736328s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 5.078315734863281e-05s
Believability | Calculation of trust value for vivo2doi took 1.239776611328125e-05s
INFO | --- Analysis for vivo2doi took 25.845045566558838s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 8.487701416015625e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.3224790096282959s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.961822509765625e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 9.5367431640625e-06s
INFO | --- Analysis for vu-wordnet took 15.053055763244629s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.15342283248901367s
Availability | VoID file availability check for vulnerapedia took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.30643701553344727s
Reputation | Calculation of the PageRank for vulnerapedia took 0.02292466163635254s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.842613220214844e-05s
Believability | Calculation of trust value for vulnerapedia took 1.2636184692382812e-05s
INFO | --- Analysis for vulnerapedia took 3.397216558456421s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 4.410743713378906e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.36619138717651367s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1444091796875e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4543533325195312e-05s
INFO | --- Analysis for VVASIAK took 2.767320394515991s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 4.38690185546875e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.2813291549682617s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.0040740966796875e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 9.775161743164062e-06s
INFO | --- Analysis for Vyvasta took 2.7175374031066895s
Availability | SPARQL endpoint availability check for W3C took 9.34600830078125e-05s
Availability | VoID file availability check for W3C took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for W3C took 0.31053781509399414s
Reputation | Calculation of the PageRank for W3C took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for W3C took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for W3C took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001347064971923828s
Believability | Calculation of trust value for W3C took 1.0967254638671875e-05s
INFO | --- Analysis for w3c took 2.9673376083374023s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 9.036064147949219e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.30043601989746094s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00010752677917480469s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 9.775161743164062e-06s
INFO | --- Analysis for w3c-wordnet took 4.023982048034668s
Availability | SPARQL endpoint availability check for WarSampo took 0.3638598918914795s
Availability | VoID file availability check for WarSampo took 0.0016391277313232422s
Extra | Recovery of all triples for WarSampo took 24.308804512023926s
Performance | Total latancy measurement for WarSampo took 0.8529689311981201s
Amount of data | Number of triples check for WarSampo took 18.557806491851807s
Interoperability | New terms check for WarSampo took 3.812269449234009s
Versatility | Languages check for WarSampo took 51.34898638725281s
Interpretability | Number of blank nodes check for WarSampo took 18.480923414230347s
Security | Check HTTPS for WarSampo took 0.41486549377441406s
Interpretability | RDF structures check for WarSampo took 0.21210765838623047s
Versatility | Serialization formats check for WarSampo took 0.20157074928283691s
Availability | RDF dump link check for WarSampo took 1.1172692775726318s
License | MR license check for WarSampo took 0.19953346252441406s
License | HR license check for WarSampo took 43.52405333518982s
Amount of data | Number of property check for WarSampo took 0.2160935401916504s
Understandability | Number of label check for WarSampo took 9.006027460098267s
Understandability | URI regex check for WarSampo took 0.36144495010375977s
Understandability | Vocabs check for WarSampo took 0.1616520881652832s
Verifiability | Authors check for WarSampo took 0.19401168823242188s
Verifiability | Publishers check for WarSampo took 0.2361302375793457s
Performance | Throughput check for WarSampo took 11.073614597320557s
Amount of data | Check the number of entities for WarSampo took 15.802158832550049s
Verifiability | Contribs. check for WarSampo took 0.20699620246887207s
Interlinking | sameAs chians check for WarSampo took 0.2102363109588623s
Interlinking | skos check for WarSampo took 0.21590495109558105s
Interlinking | skos check for WarSampo took 0.16039538383483887s
Timeliness | dataset update frequency check for WarSampo took 0.16685819625854492s
Currency | Creation date check for WarSampo took 0.3691227436065674s
Currency | Modification date check for WarSampo took 0.3738868236541748s
Rep.Conc. | URIs length for WarSampo took 48.9636332988739s
Interoperability | New vocabularies check for WarSampo took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.21359872817993164s
Accuracy | Check Functional Property for WarSampo took 0.20777297019958496s
Accuracy | Check Inverse Functional Property for WarSampo took 0.17531085014343262s
Accuracy | Check Empty annotation labels for WarSampo took 10.752746105194092s
Accuracy | Check White space in annotation for WarSampo took 2.2188527584075928s
Accuracy | Check Datatype consistency for WarSampo took 5.270908355712891s
Consistency | Disjoint class check for WarSampo took 0.21659421920776367s
Consistency | Check Misplaced properties for WarSampo took 19.95571780204773s
Consistency | Check Ontology hijacking for WarSampo took 18.616907596588135s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.341602087020874s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.563197374343872s
Conciseness | Check Extensional conciseness for WarSampo took 2.9157564640045166s
Conciseness | Check Intensional conciseness for WarSampo took 0.2810211181640625s
Security | Sign check for WarSampo took 0.1539905071258545s
Availability | Check URIs Dereferenciability for WarSampo took 2.5380702018737793s
Completeness | Calculation of interlinking completeness for WarSampo took 0.4896233081817627s
Reputation | Calculation of the PageRank for WarSampo took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for WarSampo took 1.239776611328125e-05s
INFO | --- Analysis for warsampo took 884.6142981052399s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.417428255081177s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.29088473320007324s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.867813110351562e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.2874603271484375e-05s
INFO | --- Analysis for wasabi took 54.996875524520874s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.7441508769989014s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0004563331604003906s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 112.17234802246094s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.9830241203308105s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.160581827163696s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 14.219776630401611s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.220516204834s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.038343906402588s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.2482471466064453s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 9.223626136779785s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.19869041442871094s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.2116847038269043s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.1741282939911s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.21961259841918945s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 2.0015361309051514s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 0.4581472873687744s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.1898050308227539s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.2096118927001953s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.23624587059020996s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.218276023864746s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 7.653236389160156e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.20165610313415527s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.20643019676208496s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.5146160125732422s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.43721628189086914s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 4.751142501831055s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.49282097816467285s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.24628257751464844s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 145.87296271324158s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.21627306938171387s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.21487140655517578s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.18473219871520996s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 38.36635398864746s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.687220335006714s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.612912654876709s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.21644210815429688s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 86.84761834144592s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.328965663909912s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 30.462687015533447s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.328974962234497s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 86.40405797958374s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.813037872314453s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.5058743953704834s
Security | Sign check for FAO water areas classification as linked data @PSNC took 0.6132512092590332s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 10.230924129486084s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.4508981704711914s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.021228790283203125s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for Water_Areas_Classification took 2249.699911594391s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.17917108535766602s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.0004837512969970703s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 118.30423760414124s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.9936885833740234s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 8.896849393844604s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 14.073206663131714s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.1702778339386s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 1.9545490741729736s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.20880770683288574s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 7.21975564956665s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.20991754531860352s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.18021464347839355s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.21015071868896s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.20140600204467773s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 1.1861023902893066s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 0.6192545890808105s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.2143077850341797s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.21870017051696777s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.22954750061035156s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.63285207748413s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 7.104873657226562e-05s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.20273232460021973s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.19547796249389648s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.5029215812683105s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.40400123596191406s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 3.432901382446289s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.47704219818115234s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.251767635345459s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 149.53064632415771s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 1.3113021850585938e-05s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.20629119873046875s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.18004870414733887s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.1939699649810791s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 36.29827880859375s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.7051074504852295s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.7151498794555664s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.197113037109375s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 86.08498883247375s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.301952838897705s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 34.67993998527527s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.3161051273345947s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 87.21667218208313s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.8443853855133057s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5578639507293701s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 0.17845797538757324s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 9.47439956665039s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.8374028205871582s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.021126747131347656s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.0013580322265625e-05s
INFO | --- Analysis for Water_Buffer took 2252.812884569168s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.21174025535583496s
Availability | VoID file availability check for WebIsALOD took 0.0006711483001708984s
Extra | Recovery of all triples for WebIsALOD took 1.4785468578338623s
Performance | Total latancy measurement for WebIsALOD took 0.46059608459472656s
Amount of data | Number of triples check for WebIsALOD took 29.06008219718933s
Interoperability | New terms check for WebIsALOD took 26.222705364227295s
Versatility | Languages check for WebIsALOD took 61.25399303436279s
Interpretability | Number of blank nodes check for WebIsALOD took 0.11693859100341797s
Interpretability | RDF structures check for WebIsALOD took 0.14647197723388672s
Versatility | Serialization formats check for WebIsALOD took 0.13154387474060059s
Availability | RDF dump link check for WebIsALOD took 1.5054678916931152s
License | MR license check for WebIsALOD took 0.10376405715942383s
License | HR license check for WebIsALOD took 18.30461549758911s
Amount of data | Number of property check for WebIsALOD took 0.14136528968811035s
Understandability | Number of label check for WebIsALOD took 0.35408830642700195s
Understandability | URI regex check for WebIsALOD took 0.17030024528503418s
Understandability | Vocabs check for WebIsALOD took 0.13915705680847168s
Verifiability | Authors check for WebIsALOD took 0.1359879970550537s
Verifiability | Publishers check for WebIsALOD took 0.1217648983001709s
Performance | Throughput check for WebIsALOD took 10.621013164520264s
Amount of data | Check the number of entities for WebIsALOD took 0.00012803077697753906s
Verifiability | Contribs. check for WebIsALOD took 0.12367653846740723s
Interlinking | sameAs chians check for WebIsALOD took 0.22103357315063477s
Interlinking | skos check for WebIsALOD took 0.4617130756378174s
Interlinking | skos check for WebIsALOD took 0.08707952499389648s
Timeliness | dataset update frequency check for WebIsALOD took 0.17499017715454102s
Currency | Creation date check for WebIsALOD took 0.2835249900817871s
Currency | Modification date check for WebIsALOD took 0.23402833938598633s
Rep.Conc. | URIs length for WebIsALOD took 79.28978061676025s
Interoperability | New vocabularies check for WebIsALOD took 2.811210870742798s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.12631630897521973s
Accuracy | Check Functional Property for WebIsALOD took 0.13611960411071777s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.10961198806762695s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.47725701332092285s
Accuracy | Check White space in annotation for WebIsALOD took 0.030162811279296875s
Accuracy | Check Datatype consistency for WebIsALOD took 0.029015541076660156s
Consistency | Disjoint class check for WebIsALOD took 0.11507439613342285s
Consistency | Check Misplaced properties for WebIsALOD took 62.08492374420166s
Consistency | Misplaced classes for WebIsALOD took 0.2670464515686035s
Consistency | Check Ontology hijacking for WebIsALOD took 1.9216675758361816s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.5480175018310547s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 62.86651110649109s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.0334625244140625s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.2780632972717285s
Security | Sign check for WebIsALOD took 0.09729933738708496s
Availability | Check URIs Dereferenciability for WebIsALOD took 10.00689172744751s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.39980268478393555s
Reputation | Calculation of the PageRank for WebIsALOD took 0.022033214569091797s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 2.7512729167938232s
Believability | Calculation of trust value for WebIsALOD took 1.4066696166992188e-05s
INFO | --- Analysis for webisalod took 639.2802927494049s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 9.274482727050781e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.2809622287750244s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.021114587783813477s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 4.315376281738281e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.0967254638671875e-05s
INFO | --- Analysis for webnmasunotraveler took 8.912249565124512s
Availability | SPARQL endpoint availability check for Whisky Circle took 4.482269287109375e-05s
Availability | VoID file availability check for Whisky Circle took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.27207231521606445s
Reputation | Calculation of the PageRank for Whisky Circle took 0.02157306671142578s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010275840759277344s
Believability | Calculation of trust value for Whisky Circle took 1.1444091796875e-05s
INFO | --- Analysis for whisky-circle-info took 3.2438628673553467s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 16.34249496459961s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0008168220520019531s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.2790398597717285s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.02203845977783203s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.8623809814453125e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for WHOnto took 35.01224088668823s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.29138636589050293s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.021159887313842773s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.4809112548828125e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 9.5367431640625e-06s
INFO | --- Analysis for whonto took 8.320709466934204s
Availability | SPARQL endpoint availability check for Wikidata took 0.505469560623169s
Availability | VoID file availability check for Wikidata took 0.0005545616149902344s
Extra | Recovery of all triples for Wikidata took 46.14003324508667s
Performance | Total latancy measurement for Wikidata took 1.1575088500976562s
Amount of data | Number of triples check for Wikidata took 65.17029452323914s
Interoperability | New terms check for Wikidata took 1.9325170516967773s
Versatility | Languages check for Wikidata took 60.20130658149719s
Interpretability | Number of blank nodes check for Wikidata took 65.19794988632202s
Interpretability | RDF structures check for Wikidata took 0.25545263290405273s
Versatility | Serialization formats check for Wikidata took 0.23827242851257324s
Availability | RDF dump link check for Wikidata took 0.18123483657836914s
License | MR license check for Wikidata took 0.18479585647583008s
License | HR license check for Wikidata took 60.20722460746765s
Amount of data | Number of property check for Wikidata took 1.3192360401153564s
Understandability | Number of label check for Wikidata took 0.17058300971984863s
Understandability | URI regex check for Wikidata took 0.6030392646789551s
Understandability | Vocabs check for Wikidata took 0.21975994110107422s
Verifiability | Authors check for Wikidata took 0.24642539024353027s
Verifiability | Publishers check for Wikidata took 0.18177032470703125s
Amount of data | Check the number of entities for Wikidata took 7.319450378417969e-05s
Verifiability | Contribs. check for Wikidata took 0.16919398307800293s
Interlinking | sameAs chians check for Wikidata took 16.61148953437805s
Interlinking | skos check for Wikidata took 0.29113340377807617s
Interlinking | skos check for Wikidata took 0.18199563026428223s
Timeliness | dataset update frequency check for Wikidata took 0.19770598411560059s
Currency | Creation date check for Wikidata took 0.35755157470703125s
Currency | Modification date check for Wikidata took 0.5138921737670898s
Rep.Conc. | URIs length for Wikidata took 54.995054721832275s
Interoperability | New vocabularies check for Wikidata took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.20045208930969238s
Accuracy | Check Empty annotation labels for Wikidata took 17.6378915309906s
Accuracy | Check White space in annotation for Wikidata took 2.699495315551758s
Accuracy | Check Datatype consistency for Wikidata took 4.631689786911011s
Consistency | Disjoint class check for Wikidata took 0.1909494400024414s
Consistency | Check Misplaced properties for Wikidata took 14.691826105117798s
Consistency | Misplaced classes for Wikidata took 8.897114753723145s
Consistency | Check Ontology hijacking for Wikidata took 18.254077196121216s
Consistency | Check Invalid usage of undefined classes for Wikidata took 1.38093900680542s
Consistency | Check Invalid usage of undefined properties for Wikidata took 3.6427342891693115s
Conciseness | Check Extensional conciseness for Wikidata took 2.9312970638275146s
Conciseness | Check Intensional conciseness for Wikidata took 1.563112497329712s
Security | Sign check for Wikidata took 0.1775815486907959s
Availability | Check URIs Dereferenciability for Wikidata took 8.407968521118164s
Completeness | Calculation of interlinking completeness for Wikidata took 0.49974703788757324s
Reputation | Calculation of the PageRank for Wikidata took 0.021113872528076172s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0002968311309814453s
Interoperability | Check the re-using of existing vocabs for Wikidata took 1.9073486328125e-06s
Believability | Calculation of trust value for Wikidata took 4.5299530029296875e-06s
INFO | --- Analysis for wikidata took 847.3585166931152s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 9.322166442871094e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2913327217102051s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.295608520507812e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.0967254638671875e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.8471953868865967s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.38049912452697754s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0012712478637695312s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.3113687038421631s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.022370100021362305s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.487701416015625e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.0251998901367188e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.745276212692261s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2449779510498047s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.3117086887359619s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.021028757095336914s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.147125244140625e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.049041748046875e-05s
INFO | --- Analysis for wl-kg took 4.202145099639893s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 8.726119995117188e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.2715456485748291s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.022656679153442383s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 6.67572021484375e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.0251998901367188e-05s
INFO | --- Analysis for wn-wiki-instances took 3.400834321975708s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.12647533416748047s
Availability | VoID file availability check for World Loanword Database took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.31450796127319336s
Reputation | Calculation of the PageRank for World Loanword Database took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.295608520507812e-05s
Believability | Calculation of trust value for World Loanword Database took 1.3828277587890625e-05s
INFO | --- Analysis for wold took 2.8977129459381104s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 8.821487426757812e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.2789592742919922s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.022263765335083008s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.695487976074219e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.430511474609375e-05s
INFO | --- Analysis for woodtrick took 3.4233384132385254s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.5573592185974121s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.27262282371520996s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 4.029273986816406e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 7.534027099609375e-05s
INFO | --- Analysis for WordFormationLatin took 4.270083904266357s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 9.846687316894531e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.3200814723968506s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.021762609481811523s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010609626770019531s
Believability | Calculation of trust value for WordLift Blog EN took 1.0728836059570312e-05s
INFO | --- Analysis for wordlift-io-blog-en took 3.3772366046905518s
Availability | SPARQL endpoint availability check for WordLift IT took 8.726119995117188e-05s
Availability | VoID file availability check for WordLift IT took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.3107302188873291s
Reputation | Calculation of the PageRank for WordLift IT took 0.021012544631958008s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010657310485839844s
Believability | Calculation of trust value for WordLift IT took 9.775161743164062e-06s
INFO | --- Analysis for wordlift-io-blog-it took 3.075028419494629s
Availability | SPARQL endpoint availability check for WordNet-RDF took 9.083747863769531e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.285783052444458s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.020962238311767578s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.322166442871094e-05s
Believability | Calculation of trust value for WordNet-RDF took 9.775161743164062e-06s
INFO | --- Analysis for wordnet-rdf took 2.8648293018341064s
Availability | SPARQL endpoint availability check for wordpress took 4.744529724121094e-05s
Availability | VoID file availability check for wordpress took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for wordpress took 0.31670355796813965s
Reputation | Calculation of the PageRank for wordpress took 0.02240467071533203s
Interlinking | Calculation of Degree of Connection for wordpress took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.726119995117188e-05s
Believability | Calculation of trust value for wordpress took 1.33514404296875e-05s
INFO | --- Analysis for wordpress took 3.300014019012451s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.10720157623291016s
Availability | VoID file availability check for World Bank Linked Data took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.2987082004547119s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.02234673500061035s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012445449829101562s
Believability | Calculation of trust value for World Bank Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for world-bank-linked-data took 3.049917697906494s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 1.023346185684204s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.2812650203704834s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.020915746688842773s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0009634494781494141s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 0.00010633468627929688s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.3113021850585938e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 5.685374021530151s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 8.7738037109375e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.316861629486084s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.022768497467041016s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0008728504180908203s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 0.00010204315185546875s
Believability | Calculation of trust value for World Wide Web Foundation took 9.298324584960938e-06s
INFO | --- Analysis for world-wide-web-foundation took 4.6848742961883545s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.3603079319000244s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005786418914794922s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.483531951904297s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8182826042175293s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.24675607681274414s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.4741122722625732s
Versatility | Languages check for World War 1 as Linked Open Data took 0.35453033447265625s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23976826667785645s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.41118526458740234s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.27302980422973633s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.2587883472442627s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.647302627563477s
License | MR license check for World War 1 as Linked Open Data took 0.1990184783935547s
License | HR license check for World War 1 as Linked Open Data took 1.594109296798706s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.1966850757598877s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.4493563175201416s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.3646984100341797s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.19981718063354492s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.19705772399902344s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.2046675682067871s
Performance | Throughput check for World War 1 as Linked Open Data took 11.082216024398804s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07260656356811523s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.19878458976745605s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.23828458786010742s
Interlinking | skos check for World War 1 as Linked Open Data took 0.19285130500793457s
Interlinking | skos check for World War 1 as Linked Open Data took 0.16474676132202148s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.1690962314605713s
Currency | Creation date check for World War 1 as Linked Open Data took 0.396129846572876s
Currency | Modification date check for World War 1 as Linked Open Data took 0.24515247344970703s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 1.9871728420257568s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 4.878133535385132s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.22983598709106445s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.19722795486450195s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.15964913368225098s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.2332549095153809s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.05086851119995117s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.31635332107543945s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.2137289047241211s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6025216579437256s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.0279548168182373s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.2851011753082275s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5154471397399902s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19797992706298828s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.5381321907043457s
Security | Sign check for World War 1 as Linked Open Data took 0.17354655265808105s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1571.0797817707062s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.813042163848877s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02175450325012207s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 6.289825677871704s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.3113021850585938e-05s
INFO | --- Analysis for ww1lod took 1650.2362020015717s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.3489410877227783s
Availability | VoID file availability check for xLiD-Lexica took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.30703139305114746s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.152557373046875e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.3589859008789062e-05s
INFO | --- Analysis for xlid-lexica took 4.427026033401489s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 8.58306884765625e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.3349885940551758s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.02118396759033203s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 4.029273986816406e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.049041748046875e-05s
INFO | --- Analysis for xwn took 3.0479722023010254s
Availability | SPARQL endpoint availability check for xxx took 5.793571472167969e-05s
Availability | VoID file availability check for xxx took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for xxx took 0.27587151527404785s
Reputation | Calculation of the PageRank for xxx took 0.021884918212890625s
Interlinking | Calculation of Degree of Connection for xxx took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for xxx took 3.0994415283203125e-05s
Believability | Calculation of trust value for xxx took 1.2874603271484375e-05s
INFO | --- Analysis for xx took 2.705303430557251s
Availability | SPARQL endpoint availability check for YAGO took 4.5299530029296875e-05s
Availability | VoID file availability check for YAGO took 0.0008149147033691406s
Completeness | Calculation of interlinking completeness for YAGO took 0.3024628162384033s
Reputation | Calculation of the PageRank for YAGO took 0.0209805965423584s
Interlinking | Calculation of Degree of Connection for YAGO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001373291015625s
Believability | Calculation of trust value for YAGO took 1.2636184692382812e-05s
INFO | --- Analysis for yago took 4.728947639465332s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.7460308074951172s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.3073551654815674s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.724761962890625e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.1682510375976562e-05s
INFO | --- Analysis for yahoo_geoplanet took 11.17649531364441s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.16378450393676758s
Availability | VoID file availability check for Yale Senselab took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.29651379585266113s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.552436828613281e-05s
Believability | Calculation of trust value for Yale Senselab took 1.4781951904296875e-05s
INFO | --- Analysis for yale_senselab took 11.463851928710938s
Availability | SPARQL endpoint availability check for test-dapp-2 took 8.749961853027344e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.30582547187805176s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.24249267578125e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.239776611328125e-05s
INFO | --- Analysis for yordhis took 2.711574077606201s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.8873336315155029s
Availability | VoID file availability check for Yovisto - academic video search took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.31150388717651367s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 7.176399230957031e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 1.049041748046875e-05s
INFO | --- Analysis for yovisto took 24.73162579536438s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 9.083747863769531e-05s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.26628756523132324s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.314018249511719e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 5.245208740234375e-06s
INFO | --- Analysis for ysa took 4.081188201904297s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0003037452697753906s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.28206872940063477s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.078315734863281e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for yso took 4.323906660079956s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.220008850097656e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0003037452697753906s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.2983584403991699s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.020768404006958008s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.2901763916015625e-05s
Believability | Calculation of trust value for yso-fi-allars took 5.245208740234375e-06s
INFO | --- Analysis for yso-fi-allars took 3.244184732437134s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.315376281738281e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.2830185890197754s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.02075338363647461s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.147125244140625e-05s
Believability | Calculation of trust value for yso-fi-ysa took 5.245208740234375e-06s
INFO | --- Analysis for yso-fi-ysa took 3.0828845500946045s
Availability | SPARQL endpoint availability check for YSO places took 0.6704323291778564s
Availability | VoID file availability check for YSO places took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for YSO places took 0.30881690979003906s
Reputation | Calculation of the PageRank for YSO places took 0.020282268524169922s
Interlinking | Calculation of Degree of Connection for YSO places took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for YSO places took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for YSO places took 2.956390380859375e-05s
Believability | Calculation of trust value for YSO places took 5.245208740234375e-06s
INFO | --- Analysis for yso-paikat took 4.358985185623169s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.38690185546875e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.29201364517211914s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 4.3392181396484375e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 8.106231689453125e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 73.0514805316925s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 0.00011754035949707031s
Availability | VoID file availability check for zaragoza_turruta took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.3313109874725342s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.24249267578125e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.049041748046875e-05s
INFO | --- Analysis for zaragoza_turruta took 12.83510160446167s
Availability | SPARQL endpoint availability check for ZBW Labs took 8.749961853027344e-05s
Availability | VoID file availability check for ZBW Labs took 0.000579833984375s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.29282379150390625s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02107715606689453s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.200241088867188e-05s
Believability | Calculation of trust value for ZBW Labs took 1.33514404296875e-05s
INFO | --- Analysis for zbw-labs took 3.64955472946167s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.1568741798400879s
Availability | VoID file availability check for 20th Century Press Archives took 0.0005886554718017578s
Extra | Recovery of all triples for 20th Century Press Archives took 32.04800271987915s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7462036609649658s
Amount of data | Number of triples check for 20th Century Press Archives took 2.6069459915161133s
Interoperability | New terms check for 20th Century Press Archives took 1.9273622035980225s
Versatility | Languages check for 20th Century Press Archives took 7.776685953140259s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 1.2118253707885742s
Interpretability | RDF structures check for 20th Century Press Archives took 0.1534581184387207s
Versatility | Serialization formats check for 20th Century Press Archives took 0.13728785514831543s
Availability | RDF dump link check for 20th Century Press Archives took 0.13449740409851074s
License | MR license check for 20th Century Press Archives took 0.12587976455688477s
License | HR license check for 20th Century Press Archives took 6.062556266784668s
Amount of data | Number of property check for 20th Century Press Archives took 0.14096331596374512s
Understandability | Number of label check for 20th Century Press Archives took 0.5119340419769287s
Understandability | URI regex check for 20th Century Press Archives took 0.29614782333374023s
Understandability | Vocabs check for 20th Century Press Archives took 0.14108920097351074s
Verifiability | Authors check for 20th Century Press Archives took 0.14754247665405273s
Verifiability | Publishers check for 20th Century Press Archives took 0.15781450271606445s
Performance | Throughput check for 20th Century Press Archives took 10.92552638053894s
Amount of data | Check the number of entities for 20th Century Press Archives took 6.890296936035156e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1454453468322754s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.12331056594848633s
Interlinking | skos check for 20th Century Press Archives took 0.3529808521270752s
Interlinking | skos check for 20th Century Press Archives took 0.1885082721710205s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.16143155097961426s
Currency | Creation date check for 20th Century Press Archives took 0.27404093742370605s
Currency | Modification date check for 20th Century Press Archives took 0.28918910026550293s
Rep.Conc. | URIs length for 20th Century Press Archives took 16.99997568130493s
Interoperability | New vocabularies check for 20th Century Press Archives took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.14777612686157227s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.1603412628173828s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.15209293365478516s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 6.4912567138671875s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8852221965789795s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.08188009262085s
Consistency | Disjoint class check for 20th Century Press Archives took 0.1476302146911621s
Consistency | Check Misplaced properties for 20th Century Press Archives took 3.007646322250366s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.517378807067871s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.9598259925842285s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.4339451789855957s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.8753321170806885s
Security | Sign check for 20th Century Press Archives took 0.14072465896606445s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 971.8117127418518s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.46140122413635254s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.02284979820251465s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00011539459228515625s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 2.1457672119140625e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.0251998901367188e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1108.103006362915s
Availability | SPARQL endpoint availability check for zhishi.lemon took 8.678436279296875e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.2873401641845703s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 5.602836608886719e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.239776611328125e-05s
INFO | --- Analysis for zhishi-lemon took 24.598177433013916s
Availability | SPARQL endpoint availability check for Zhishi.me took 10.836491346359253s
Availability | VoID file availability check for Zhishi.me took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.3257334232330322s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.367134094238281e-05s
Believability | Calculation of trust value for Zhishi.me took 1.049041748046875e-05s
INFO | --- Analysis for zhishi-me took 16.052111387252808s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.3392181396484375e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.3011963367462158s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.021335601806640625s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 6.341934204101562e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.1205673217773438e-05s
INFO | --- Analysis for zitgist-musicbrainz took 3.267016649246216s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 9.512901306152344e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.001003265380859375s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.3031737804412842s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.075599670410156e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.33514404296875e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 3.000972270965576s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.29817891120910645s
Availability | VoID file availability check for performing-arts.ch took 0.000499725341796875s
Extra | Recovery of all triples for performing-arts.ch took 14.878989458084106s
Performance | Total latancy measurement for performing-arts.ch took 0.7608709335327148s
Amount of data | Number of triples check for performing-arts.ch took 53.565821409225464s
Interoperability | New terms check for performing-arts.ch took 1.4335222244262695s
Versatility | Languages check for performing-arts.ch took 60.13650989532471s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.154829263687134s
Interpretability | RDF structures check for performing-arts.ch took 0.1706845760345459s
Versatility | Serialization formats check for performing-arts.ch took 0.18010997772216797s
Availability | RDF dump link check for performing-arts.ch took 0.14223861694335938s
License | MR license check for performing-arts.ch took 0.7092492580413818s
License | HR license check for performing-arts.ch took 60.1166307926178s
Amount of data | Number of property check for performing-arts.ch took 7.095303773880005s
Understandability | Number of label check for performing-arts.ch took 18.570841073989868s
Understandability | URI regex check for performing-arts.ch took 0.28827404975891113s
Understandability | Vocabs check for performing-arts.ch took 0.1568315029144287s
Verifiability | Authors check for performing-arts.ch took 0.9609470367431641s
Verifiability | Publishers check for performing-arts.ch took 0.14777708053588867s
Performance | Throughput check for performing-arts.ch took 14.789996147155762s
Amount of data | Check the number of entities for performing-arts.ch took 7.343292236328125e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.16344785690307617s
Interlinking | sameAs chians check for performing-arts.ch took 1.7347686290740967s
Interlinking | skos check for performing-arts.ch took 0.17431902885437012s
Interlinking | skos check for performing-arts.ch took 0.16089963912963867s
Timeliness | dataset update frequency check for performing-arts.ch took 0.1646270751953125s
Currency | Creation date check for performing-arts.ch took 0.31325507164001465s
Currency | Modification date check for performing-arts.ch took 0.8990437984466553s
Rep.Conc. | URIs length for performing-arts.ch took 48.327290058135986s
Interoperability | New vocabularies check for performing-arts.ch took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.13135671615600586s
Accuracy | Check Functional Property for performing-arts.ch took 0.14662909507751465s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.15392255783081055s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.538721323013306s
Accuracy | Check White space in annotation for performing-arts.ch took 2.53957462310791s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.704065322875977s
Consistency | Disjoint class check for performing-arts.ch took 0.17172002792358398s
Consistency | Check Misplaced properties for performing-arts.ch took 0.3576221466064453s
Consistency | Misplaced classes for performing-arts.ch took 8.372920751571655s
Consistency | Check Ontology hijacking for performing-arts.ch took 49.32956647872925s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 15094.0884912014s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.8275225162506104s
Conciseness | Check Extensional conciseness for performing-arts.ch took 3.0124330520629883s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.3039216995239258s
Security | Sign check for performing-arts.ch took 0.16845059394836426s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.4847867488861084s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.853661298751831s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021060466766357422s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.71661376953125e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 2.6226043701171875e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.33514404296875e-05s
INFO | --- Analysis for performing-arts.ch took 15980.980419635773s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.415362596511841s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0007710456848144531s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.30602264404296875s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.021120309829711914s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0009555816650390625s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.2636184692382812e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.430511474609375e-05s
INFO | --- Analysis for The-AA-Thesaurus took 8.704099893569946s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.7312781810760498s
Availability | VoID file availability check for MiMoTextBase took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.29877138137817383s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.02097153663635254s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.2874603271484375e-05s
Believability | Calculation of trust value for MiMoTextBase took 7.152557373046875e-06s
INFO | --- Analysis for MiMoTextBase took 6.559019327163696s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5859880447387695s
Availability | VoID file availability check for National Library of Sweden took 0.001154184341430664s
Extra | Recovery of all triples for National Library of Sweden took 5.721894979476929s
Performance | Total latancy measurement for National Library of Sweden took 1.064007043838501s
Amount of data | Number of triples check for National Library of Sweden took 20.691662073135376s
Interoperability | New terms check for National Library of Sweden took 15.214154720306396s
Versatility | Languages check for National Library of Sweden took 0.2077493667602539s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.2430970668793s
Interpretability | RDF structures check for National Library of Sweden took 3.386639356613159s
Versatility | Serialization formats check for National Library of Sweden took 0.260098934173584s
Availability | RDF dump link check for National Library of Sweden took 0.22042417526245117s
License | MR license check for National Library of Sweden took 0.32246971130371094s
License | HR license check for National Library of Sweden took 0.34549665451049805s
Amount of data | Number of property check for National Library of Sweden took 0.21596312522888184s
Understandability | Number of label check for National Library of Sweden took 0.5027520656585693s
Understandability | URI regex check for National Library of Sweden took 0.5144875049591064s
Understandability | Vocabs check for National Library of Sweden took 0.21234631538391113s
Verifiability | Authors check for National Library of Sweden took 0.2440800666809082s
Verifiability | Publishers check for National Library of Sweden took 0.25040626525878906s
Performance | Throughput check for National Library of Sweden took 10.60691523551941s
Amount of data | Check the number of entities for National Library of Sweden took 0.0001342296600341797s
Verifiability | Contribs. check for National Library of Sweden took 0.24139666557312012s
Interlinking | sameAs chians check for National Library of Sweden took 0.2363429069519043s
Interlinking | skos check for National Library of Sweden took 0.34804320335388184s
Interlinking | skos check for National Library of Sweden took 0.20662212371826172s
Timeliness | dataset update frequency check for National Library of Sweden took 0.22763276100158691s
Currency | Creation date check for National Library of Sweden took 0.49746227264404297s
Currency | Modification date check for National Library of Sweden took 0.4797065258026123s
Rep.Conc. | URIs length for National Library of Sweden took 81.47416996955872s
Interoperability | New vocabularies check for National Library of Sweden took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.21804499626159668s
Accuracy | Check Functional Property for National Library of Sweden took 0.243056058883667s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.2661013603210449s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2676541805267334s
Consistency | Disjoint class check for National Library of Sweden took 0.24320745468139648s
Consistency | Check Misplaced properties for National Library of Sweden took 60.09751868247986s
Consistency | Misplaced classes for National Library of Sweden took 1.1367175579071045s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.3605291843414307s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.2332301139831543s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 61.054582595825195s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.28937649726867676s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.32998108863830566s
Security | Sign check for National Library of Sweden took 0.4229423999786377s
Availability | Check URIs Dereferenciability for National Library of Sweden took 10.306457042694092s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.41791725158691406s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.5735626220703125e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library of Sweden took 8.58306884765625e-06s
INFO | --- Analysis for NLS took 1367.275630235672s
Availability | SPARQL endpoint availability check for Japan Search took 0.9148757457733154s
Availability | VoID file availability check for Japan Search took 0.0005218982696533203s
Extra | Recovery of all triples for Japan Search took 3.5184009075164795s
Performance | Total latancy measurement for Japan Search took 2.734783887863159s
Amount of data | Number of triples check for Japan Search took 5.11016058921814s
Interoperability | New terms check for Japan Search took 3.5536575317382812s
Versatility | Languages check for Japan Search took 0.7369575500488281s
Interpretability | Number of blank nodes check for Japan Search took 12.057767391204834s
Interpretability | RDF structures check for Japan Search took 0.4029209613800049s
Versatility | Serialization formats check for Japan Search took 0.3952803611755371s
Availability | RDF dump link check for Japan Search took 0.316605806350708s
License | MR license check for Japan Search took 0.5069375038146973s
License | HR license check for Japan Search took 10.761528253555298s
Amount of data | Number of property check for Japan Search took 0.2739851474761963s
Understandability | Number of label check for Japan Search took 2.873354434967041s
Understandability | URI regex check for Japan Search took 0.556190013885498s
Understandability | Vocabs check for Japan Search took 0.28710484504699707s
Verifiability | Authors check for Japan Search took 0.29792308807373047s
Verifiability | Publishers check for Japan Search took 0.850477933883667s
Performance | Throughput check for Japan Search took 11.57051396369934s
Amount of data | Check the number of entities for Japan Search took 3.24249267578125e-05s
Verifiability | Contribs. check for Japan Search took 0.2647559642791748s
Interlinking | sameAs chians check for Japan Search took 0.29116249084472656s
Interlinking | skos check for Japan Search took 0.30098748207092285s
Interlinking | skos check for Japan Search took 0.28577303886413574s
Timeliness | dataset update frequency check for Japan Search took 0.41477084159851074s
Currency | Creation date check for Japan Search took 0.5743937492370605s
Currency | Modification date check for Japan Search took 0.5555257797241211s
Rep.Conc. | URIs length for Japan Search took 14.40718412399292s
Interoperability | New vocabularies check for Japan Search took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7556142807006836s
Accuracy | Check Empty annotation labels for Japan Search took 1.7701785564422607s
Accuracy | Check White space in annotation for Japan Search took 0.029549360275268555s
Accuracy | Check Datatype consistency for Japan Search took 0.029383420944213867s
Consistency | Disjoint class check for Japan Search took 0.2639949321746826s
Consistency | Check Misplaced properties for Japan Search took 12.372700691223145s
Consistency | Misplaced classes for Japan Search took 1.0537753105163574s
Consistency | Check Ontology hijacking for Japan Search took 3.4375076293945312s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.276658296585083s
Consistency | Check Invalid usage of undefined properties for Japan Search took 11.568306922912598s
Conciseness | Check Extensional conciseness for Japan Search took 0.04974222183227539s
Conciseness | Check Intensional conciseness for Japan Search took 0.2744734287261963s
Security | Sign check for Japan Search took 0.7649848461151123s
Availability | Check URIs Dereferenciability for Japan Search took 9.000335216522217s
Completeness | Calculation of interlinking completeness for Japan Search took 0.40708208084106445s
Reputation | Calculation of the PageRank for Japan Search took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for Japan Search took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.71661376953125e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.6689300537109375e-06s
Believability | Calculation of trust value for Japan Search took 1.3589859008789062e-05s
INFO | --- Analysis for Japan-Search took 410.2499339580536s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.982046127319336s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.2787752151489258s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020947694778442383s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.2159347534179688e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.0967254638671875e-05s
INFO | --- Analysis for Rijksmuseum took 5.850374937057495s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.5904619693756104s
Availability | VoID file availability check for Finnish Public Libraries took 0.0005464553833007812s
Extra | Recovery of all triples for Finnish Public Libraries took 17.38225793838501s
Performance | Total latancy measurement for Finnish Public Libraries took 0.9608035087585449s
Amount of data | Number of triples check for Finnish Public Libraries took 60.10983395576477s
Interoperability | New terms check for Finnish Public Libraries took 17.32272744178772s
Versatility | Languages check for Finnish Public Libraries took 60.328715085983276s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.27854299545288s
Interpretability | RDF structures check for Finnish Public Libraries took 0.42668700218200684s
Versatility | Serialization formats check for Finnish Public Libraries took 0.24556922912597656s
Availability | RDF dump link check for Finnish Public Libraries took 0.21975421905517578s
License | MR license check for Finnish Public Libraries took 0.3005797863006592s
License | HR license check for Finnish Public Libraries took 60.208123445510864s
Amount of data | Number of property check for Finnish Public Libraries took 0.38362884521484375s
Understandability | Number of label check for Finnish Public Libraries took 20.53140139579773s
Understandability | URI regex check for Finnish Public Libraries took 0.39364075660705566s
Understandability | Vocabs check for Finnish Public Libraries took 0.27680253982543945s
Verifiability | Authors check for Finnish Public Libraries took 0.39075422286987305s
Verifiability | Publishers check for Finnish Public Libraries took 0.30239343643188477s
Performance | Throughput check for Finnish Public Libraries took 10.78946328163147s
Amount of data | Check the number of entities for Finnish Public Libraries took 4.172325134277344e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.1379387378692627s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.5370750427246094s
Interlinking | skos check for Finnish Public Libraries took 0.1346144676208496s
Interlinking | skos check for Finnish Public Libraries took 0.15599966049194336s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.12742328643798828s
Currency | Creation date check for Finnish Public Libraries took 0.3401143550872803s
Currency | Modification date check for Finnish Public Libraries took 0.27054667472839355s
Rep.Conc. | URIs length for Finnish Public Libraries took 85.02333354949951s
Interoperability | New vocabularies check for Finnish Public Libraries took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.3327491283416748s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 8.30767822265625s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.2128677368164062s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.389163970947266s
Consistency | Disjoint class check for Finnish Public Libraries took 0.23270654678344727s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.417957067489624s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 15.032642602920532s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.4546263217926025s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.474289417266846s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.8333559036254883s
Security | Sign check for Finnish Public Libraries took 0.285815954208374s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 0.952890157699585s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.4791393280029297s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.1205673217773438e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 1.9073486328125e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.3113021850585938e-05s
INFO | --- Analysis for FI-Library took 694.4614405632019s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.400653839111328s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.00048160552978515625s
Extra | Recovery of all triples for Shanghai Library Open Data Platform took 10.43785834312439s
Performance | Total latancy measurement for Shanghai Library Open Data Platform took 3.4372098445892334s
Amount of data | Number of triples check for Shanghai Library Open Data Platform took 2.158492088317871s
Interoperability | New terms check for Shanghai Library Open Data Platform took 2.992851972579956s
Versatility | Languages check for Shanghai Library Open Data Platform took 60.710484981536865s
Interpretability | Number of blank nodes check for Shanghai Library Open Data Platform took 2.010120153427124s
Interpretability | RDF structures check for Shanghai Library Open Data Platform took 1.2210886478424072s
Versatility | Serialization formats check for Shanghai Library Open Data Platform took 0.9129221439361572s
Availability | RDF dump link check for Shanghai Library Open Data Platform took 0.8029212951660156s
License | MR license check for Shanghai Library Open Data Platform took 1.124342441558838s
License | HR license check for Shanghai Library Open Data Platform took 32.4109206199646s
Amount of data | Number of property check for Shanghai Library Open Data Platform took 0.7360641956329346s
Understandability | Number of label check for Shanghai Library Open Data Platform took 1.4558053016662598s
Understandability | URI regex check for Shanghai Library Open Data Platform took 1.5573689937591553s
Understandability | Vocabs check for Shanghai Library Open Data Platform took 0.7355878353118896s
Verifiability | Authors check for Shanghai Library Open Data Platform took 0.8274714946746826s
Verifiability | Publishers check for Shanghai Library Open Data Platform took 0.7708072662353516s
Performance | Throughput check for Shanghai Library Open Data Platform took 14.079930305480957s
Amount of data | Check the number of entities for Shanghai Library Open Data Platform took 6.961822509765625e-05s
Verifiability | Contribs. check for Shanghai Library Open Data Platform took 0.7144746780395508s
Interlinking | sameAs chians check for Shanghai Library Open Data Platform took 0.7520813941955566s
Interlinking | skos check for Shanghai Library Open Data Platform took 1.026538610458374s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.6840353012084961s
Timeliness | dataset update frequency check for Shanghai Library Open Data Platform took 0.849334716796875s
Currency | Creation date check for Shanghai Library Open Data Platform took 1.622908353805542s
Currency | Modification date check for Shanghai Library Open Data Platform took 1.4767954349517822s
Rep.Conc. | URIs length for Shanghai Library Open Data Platform took 11.811933040618896s
Interoperability | New vocabularies check for Shanghai Library Open Data Platform took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for Shanghai Library Open Data Platform took 0.698068380355835s
Accuracy | Check Functional Property for Shanghai Library Open Data Platform took 0.7488064765930176s
Accuracy | Check Inverse Functional Property for Shanghai Library Open Data Platform took 0.7555193901062012s
Accuracy | Check Empty annotation labels for Shanghai Library Open Data Platform took 3.1120798587799072s
Accuracy | Check White space in annotation for Shanghai Library Open Data Platform took 0.06469058990478516s
Accuracy | Check Datatype consistency for Shanghai Library Open Data Platform took 0.13814258575439453s
Consistency | Disjoint class check for Shanghai Library Open Data Platform took 0.9086945056915283s
Consistency | Check Misplaced properties for Shanghai Library Open Data Platform took 6.340693235397339s
Consistency | Misplaced classes for Shanghai Library Open Data Platform took 1.341012954711914s
Consistency | Check Ontology hijacking for Shanghai Library Open Data Platform took 5.988943815231323s
Consistency | Check Invalid usage of undefined classes for Shanghai Library Open Data Platform took 1.40645432472229s
Consistency | Check Invalid usage of undefined properties for Shanghai Library Open Data Platform took 6.966253042221069s
Conciseness | Check Extensional conciseness for Shanghai Library Open Data Platform took 0.1525435447692871s
Conciseness | Check Intensional conciseness for Shanghai Library Open Data Platform took 1.1749427318572998s
Security | Sign check for Shanghai Library Open Data Platform took 0.9842731952667236s
Availability | Check URIs Dereferenciability for Shanghai Library Open Data Platform took 9.910301208496094s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.3207423686981201s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.022156476974487305s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for Shanghai Library Open Data Platform took 1.9073486328125e-06s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.3113021850585938e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 303.5314612388611s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.4080264568328857s
Availability | VoID file availability check for National Library Netherlands took 0.0006220340728759766s
Extra | Recovery of all triples for National Library Netherlands took 1.0354421138763428s
Performance | Total latancy measurement for National Library Netherlands took 0.7685434818267822s
Amount of data | Number of triples check for National Library Netherlands took 1.6941726207733154s
Interoperability | New terms check for National Library Netherlands took 2.2190053462982178s
Versatility | Languages check for National Library Netherlands took 58.13105607032776s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.17598485946655273s
Interpretability | RDF structures check for National Library Netherlands took 0.3510575294494629s
Versatility | Serialization formats check for National Library Netherlands took 0.18673491477966309s
Availability | RDF dump link check for National Library Netherlands took 0.19227385520935059s
License | MR license check for National Library Netherlands took 0.366929292678833s
License | HR license check for National Library Netherlands took 58.13346242904663s
Amount of data | Number of property check for National Library Netherlands took 0.1570277214050293s
Understandability | Number of label check for National Library Netherlands took 9.125393152236938s
Understandability | URI regex check for National Library Netherlands took 0.29929280281066895s
Understandability | Vocabs check for National Library Netherlands took 0.17422842979431152s
Verifiability | Authors check for National Library Netherlands took 0.17146539688110352s
Verifiability | Publishers check for National Library Netherlands took 0.17245888710021973s
Performance | Throughput check for National Library Netherlands took 10.655316352844238s
Amount of data | Check the number of entities for National Library Netherlands took 8.153915405273438e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.1634047031402588s
Interlinking | sameAs chians check for National Library Netherlands took 0.4153316020965576s
Interlinking | skos check for National Library Netherlands took 0.20401716232299805s
Interlinking | skos check for National Library Netherlands took 0.1792299747467041s
Timeliness | dataset update frequency check for National Library Netherlands took 0.1607646942138672s
Currency | Creation date check for National Library Netherlands took 0.34873437881469727s
Currency | Modification date check for National Library Netherlands took 0.3430769443511963s
Rep.Conc. | URIs length for National Library Netherlands took 4.720200300216675s
Interoperability | New vocabularies check for National Library Netherlands took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.16546416282653809s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.9197814464569092s
Accuracy | Check White space in annotation for National Library Netherlands took 0.02744579315185547s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.028501033782958984s
Consistency | Disjoint class check for National Library Netherlands took 0.22399210929870605s
Consistency | Check Misplaced properties for National Library Netherlands took 3.6526684761047363s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.9017536640167236s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.336317539215088s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.5527160167694092s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.030942678451538086s
Security | Sign check for National Library Netherlands took 0.185927152633667s
Availability | Check URIs Dereferenciability for National Library Netherlands took 6.139478445053101s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.3049354553222656s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.022412776947021484s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.3126602172851562e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.7404556274414062e-05s
INFO | --- Analysis for National-Library-Netherlands took 249.38725590705872s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.485184907913208s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.28089404106140137s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.021369457244873047s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.4066696166992188e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.33514404296875e-05s
INFO | --- Analysis for Antique-Renaissance took 5.91623330116272s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 7.100651741027832s
Availability | VoID file availability check for ARTSDATA.CA took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.28830671310424805s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.33514404296875e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.3589859008789062e-05s
INFO | --- Analysis for ARTSDATA-CA took 13.307942867279053s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.0947422981262207s
Availability | VoID file availability check for Architecture of Knowledge took 0.0003008842468261719s
Extra | Recovery of all triples for Architecture of Knowledge took 60.10414457321167s
Performance | Total latancy measurement for Architecture of Knowledge took 0.22162389755249023s
Amount of data | Number of triples check for Architecture of Knowledge took 4.8876953125s
Interoperability | New terms check for Architecture of Knowledge took 5.405757427215576s
Versatility | Languages check for Architecture of Knowledge took 62.32006335258484s
Interpretability | Number of blank nodes check for Architecture of Knowledge took 0.0978848934173584s
Interpretability | RDF structures check for Architecture of Knowledge took 0.3000192642211914s
Versatility | Serialization formats check for Architecture of Knowledge took 0.08141207695007324s
Availability | RDF dump link check for Architecture of Knowledge took 0.03319120407104492s
License | MR license check for Architecture of Knowledge took 0.11145949363708496s
License | HR license check for Architecture of Knowledge took 60.1782488822937s
Amount of data | Number of property check for Architecture of Knowledge took 0.09136366844177246s
Understandability | Number of label check for Architecture of Knowledge took 1.6052865982055664s
Understandability | URI regex check for Architecture of Knowledge took 0.07160544395446777s
Understandability | Vocabs check for Architecture of Knowledge took 0.03708457946777344s
Verifiability | Authors check for Architecture of Knowledge took 0.05610060691833496s
Verifiability | Publishers check for Architecture of Knowledge took 0.03783726692199707s
Performance | Throughput check for Architecture of Knowledge took 10.43790054321289s
Amount of data | Check the number of entities for Architecture of Knowledge took 4.935264587402344e-05s
Verifiability | Contribs. check for Architecture of Knowledge took 0.046784400939941406s
Interlinking | sameAs chians check for Architecture of Knowledge took 0.07356452941894531s
Interlinking | skos check for Architecture of Knowledge took 0.1360611915588379s
Interlinking | skos check for Architecture of Knowledge took 0.041924476623535156s
Timeliness | dataset update frequency check for Architecture of Knowledge took 0.0341944694519043s
Currency | Creation date check for Architecture of Knowledge took 0.16647601127624512s
Currency | Modification date check for Architecture of Knowledge took 0.16156005859375s
Rep.Conc. | URIs length for Architecture of Knowledge took 90.87728929519653s
Interoperability | New vocabularies check for Architecture of Knowledge took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Architecture of Knowledge took 0.0740199089050293s
Accuracy | Check Functional Property for Architecture of Knowledge took 0.10363125801086426s
Accuracy | Check Inverse Functional Property for Architecture of Knowledge took 0.06493330001831055s
Accuracy | Check Empty annotation labels for Architecture of Knowledge took 48.94231343269348s
Accuracy | Check White space in annotation for Architecture of Knowledge took 3.121293067932129s
Consistency | Disjoint class check for Architecture of Knowledge took 0.15144133567810059s
Consistency | Check Misplaced properties for Architecture of Knowledge took 28.335273265838623s
Consistency | Misplaced classes for Architecture of Knowledge took 0.10899806022644043s
Consistency | Check Ontology hijacking for Architecture of Knowledge took 60.19626569747925s
Consistency | Check Invalid usage of undefined properties for Architecture of Knowledge took 47.24763083457947s
Conciseness | Check Extensional conciseness for Architecture of Knowledge took 0.0001595020294189453s
Security | Sign check for Architecture of Knowledge took 60.17821717262268s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.7504596710205078s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.021523475646972656s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 2.574920654296875e-05s
Interoperability | Check the re-using of existing vocabs for Architecture of Knowledge took 1.9073486328125e-06s
Believability | Calculation of trust value for Architecture of Knowledge took 1.4066696166992188e-05s
INFO | --- Analysis for ArCo took 1300.2982444763184s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.41889166831970215s
Availability | VoID file availability check for ConfermentSampo took 0.0004999637603759766s
Extra | Recovery of all triples for ConfermentSampo took 18.377464532852173s
Performance | Total latancy measurement for ConfermentSampo took 0.8375577926635742s
Amount of data | Number of triples check for ConfermentSampo took 8.751965522766113s
Interoperability | New terms check for ConfermentSampo took 2.7750487327575684s
Versatility | Languages check for ConfermentSampo took 26.392696142196655s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.098166227340698s
Security | Check HTTPS for ConfermentSampo took 0.4188551902770996s
Interpretability | RDF structures check for ConfermentSampo took 0.22201752662658691s
Versatility | Serialization formats check for ConfermentSampo took 0.21981191635131836s
Availability | RDF dump link check for ConfermentSampo took 3.086848497390747s
License | MR license check for ConfermentSampo took 0.20022320747375488s
License | HR license check for ConfermentSampo took 0.22756147384643555s
Amount of data | Number of property check for ConfermentSampo took 0.20985960960388184s
Understandability | Number of label check for ConfermentSampo took 5.561256647109985s
Understandability | URI regex check for ConfermentSampo took 0.38736677169799805s
Understandability | Vocabs check for ConfermentSampo took 0.16343975067138672s
Verifiability | Authors check for ConfermentSampo took 0.23853135108947754s
Verifiability | Publishers check for ConfermentSampo took 0.21784567832946777s
Performance | Throughput check for ConfermentSampo took 11.023638486862183s
Amount of data | Check the number of entities for ConfermentSampo took 4.012923240661621s
Verifiability | Contribs. check for ConfermentSampo took 0.15935230255126953s
Interlinking | sameAs chians check for ConfermentSampo took 0.4328639507293701s
Interlinking | skos check for ConfermentSampo took 0.1659996509552002s
Interlinking | skos check for ConfermentSampo took 0.16058754920959473s
Timeliness | dataset update frequency check for ConfermentSampo took 0.1694340705871582s
Currency | Creation date check for ConfermentSampo took 0.36444735527038574s
Currency | Modification date check for ConfermentSampo took 0.3760964870452881s
Rep.Conc. | URIs length for ConfermentSampo took 34.965816020965576s
Interoperability | New vocabularies check for ConfermentSampo took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.2017199993133545s
Accuracy | Check Functional Property for ConfermentSampo took 0.20102143287658691s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.1560220718383789s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.949773073196411s
Accuracy | Check White space in annotation for ConfermentSampo took 3.0243072509765625s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.127391815185547s
Consistency | Disjoint class check for ConfermentSampo took 0.1735517978668213s
Consistency | Check Misplaced properties for ConfermentSampo took 6.674247741699219s
Consistency | Check Ontology hijacking for ConfermentSampo took 15.332706212997437s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.4656591415405273s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5738945007324219s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.9294981956481934s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.2062535285949707s
Security | Sign check for ConfermentSampo took 0.1559441089630127s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1467.6386358737946s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.5484247207641602s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.021904706954956055s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 7.295608520507812e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.6927719116210938e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 1.9073486328125e-06s
Believability | Calculation of trust value for ConfermentSampo took 7.319450378417969e-05s
INFO | --- Analysis for ConfermentSampo took 1765.9465701580048s
Availability | SPARQL endpoint availability check for Museum Finland took 0.24135565757751465s
Availability | VoID file availability check for Museum Finland took 0.0006194114685058594s
Extra | Recovery of all triples for Museum Finland took 4.471262693405151s
Performance | Total latancy measurement for Museum Finland took 0.8217964172363281s
Amount of data | Number of triples check for Museum Finland took 0.35044002532958984s
Interoperability | New terms check for Museum Finland took 1.7652006149291992s
Versatility | Languages check for Museum Finland took 0.7028162479400635s
Interpretability | Number of blank nodes check for Museum Finland took 0.34242725372314453s
Security | Check HTTPS for Museum Finland took 0.24037885665893555s
Interpretability | RDF structures check for Museum Finland took 0.6825997829437256s
Versatility | Serialization formats check for Museum Finland took 0.20242929458618164s
Availability | RDF dump link check for Museum Finland took 0.1536707878112793s
License | MR license check for Museum Finland took 0.17977523803710938s
License | HR license check for Museum Finland took 0.3635845184326172s
Amount of data | Number of property check for Museum Finland took 0.19680166244506836s
Understandability | Number of label check for Museum Finland took 0.4335451126098633s
Understandability | URI regex check for Museum Finland took 0.3268778324127197s
Understandability | Vocabs check for Museum Finland took 0.159637451171875s
Verifiability | Authors check for Museum Finland took 0.16911721229553223s
Verifiability | Publishers check for Museum Finland took 0.1595778465270996s
Performance | Throughput check for Museum Finland took 10.866458654403687s
Amount of data | Check the number of entities for Museum Finland took 8.082389831542969e-05s
Verifiability | Contribs. check for Museum Finland took 0.15977263450622559s
Interlinking | sameAs chians check for Museum Finland took 0.1616044044494629s
Interlinking | skos check for Museum Finland took 0.16945624351501465s
Interlinking | skos check for Museum Finland took 0.15650629997253418s
Timeliness | dataset update frequency check for Museum Finland took 0.1673123836517334s
Currency | Creation date check for Museum Finland took 0.3554987907409668s
Currency | Modification date check for Museum Finland took 0.36628293991088867s
Rep.Conc. | URIs length for Museum Finland took 3.580202102661133s
Interoperability | New vocabularies check for Museum Finland took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.20221662521362305s
Accuracy | Check Functional Property for Museum Finland took 0.15159273147583008s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.15896368026733398s
Accuracy | Check Empty annotation labels for Museum Finland took 0.9627108573913574s
Accuracy | Check White space in annotation for Museum Finland took 0.06199049949645996s
Accuracy | Check Datatype consistency for Museum Finland took 0.9737977981567383s
Consistency | Disjoint class check for Museum Finland took 0.15474414825439453s
Consistency | Check Misplaced properties for Museum Finland took 0.6243937015533447s
Consistency | Check Ontology hijacking for Museum Finland took 2.2205700874328613s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.456714391708374s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.805635690689087s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6972393989562988s
Conciseness | Check Intensional conciseness for Museum Finland took 0.26631641387939453s
Security | Sign check for Museum Finland took 0.15963387489318848s
Availability | Check URIs Dereferenciability for Museum Finland took 2627.7013823986053s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.8981029987335205s
Reputation | Calculation of the PageRank for Museum Finland took 0.021047353744506836s
Interlinking | Calculation of Degree of Connection for Museum Finland took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.0967254638671875e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.384185791015625e-06s
Believability | Calculation of trust value for Museum Finland took 7.62939453125e-06s
INFO | --- Analysis for FI-Museum took 2682.742973804474s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.2099609375s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005946159362792969s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.791385412216187s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8318512439727783s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 29.789674520492554s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.932979106903076s
Versatility | Languages check for Mapping Manuscript Migrations took 75.3257896900177s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.30000925064087s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.4187660217285156s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.1914536952972412s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.19465327262878418s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.1521763801574707s
License | MR license check for Mapping Manuscript Migrations took 0.20297646522521973s
License | HR license check for Mapping Manuscript Migrations took 1.8341214656829834s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.18999123573303223s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.744901418685913s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.36474061012268066s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.15437889099121094s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19830870628356934s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.19088244438171387s
Performance | Throughput check for Mapping Manuscript Migrations took 11.202932119369507s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0445687770843506s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.16282963752746582s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5132761001586914s
Interlinking | skos check for Mapping Manuscript Migrations took 0.15973544120788574s
Interlinking | skos check for Mapping Manuscript Migrations took 0.15007495880126953s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.1605062484741211s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3645792007446289s
Currency | Modification date check for Mapping Manuscript Migrations took 0.19814252853393555s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 48.10308074951172s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.16694092750549316s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.16669964790344238s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.16650676727294922s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.417789220809937s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4474689960479736s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.658845663070679s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.1982719898223877s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 22.29192280769348s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.26021432876587s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.5651893615722656s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.597017765045166s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.920614004135132s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.21850347518920898s
Security | Sign check for Mapping Manuscript Migrations took 0.15258502960205078s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1677.1104321479797s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.492595911026001s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.021198749542236328s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 6.723403930664062e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.8596649169921875e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 1.6689300537109375e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.430511474609375e-05s
INFO | --- Analysis for MMM took 2078.9067838191986s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.24909424781799316s
Availability | VoID file availability check for Semantic Kalevala took 0.0005550384521484375s
Extra | Recovery of all triples for Semantic Kalevala took 5.9493889808654785s
Performance | Total latancy measurement for Semantic Kalevala took 0.833115816116333s
Amount of data | Number of triples check for Semantic Kalevala took 0.43942928314208984s
Interoperability | New terms check for Semantic Kalevala took 1.9751691818237305s
Versatility | Languages check for Semantic Kalevala took 0.9975442886352539s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.3860464096069336s
Security | Check HTTPS for Semantic Kalevala took 0.38638949394226074s
Interpretability | RDF structures check for Semantic Kalevala took 0.3002345561981201s
Versatility | Serialization formats check for Semantic Kalevala took 0.2275691032409668s
Availability | RDF dump link check for Semantic Kalevala took 0.1722853183746338s
License | MR license check for Semantic Kalevala took 0.20299792289733887s
License | HR license check for Semantic Kalevala took 1.0353162288665771s
Amount of data | Number of property check for Semantic Kalevala took 0.18816876411437988s
Understandability | Number of label check for Semantic Kalevala took 0.4883244037628174s
Understandability | URI regex check for Semantic Kalevala took 0.3267817497253418s
Understandability | Vocabs check for Semantic Kalevala took 0.16777992248535156s
Verifiability | Authors check for Semantic Kalevala took 0.165726900100708s
Verifiability | Publishers check for Semantic Kalevala took 0.16783404350280762s
Performance | Throughput check for Semantic Kalevala took 11.014136552810669s
Amount of data | Check the number of entities for Semantic Kalevala took 7.128715515136719e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.16616368293762207s
Interlinking | sameAs chians check for Semantic Kalevala took 0.2044360637664795s
Interlinking | skos check for Semantic Kalevala took 0.26372671127319336s
Interlinking | skos check for Semantic Kalevala took 0.16324186325073242s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.1686995029449463s
Currency | Creation date check for Semantic Kalevala took 0.3554503917694092s
Currency | Modification date check for Semantic Kalevala took 0.35587048530578613s
Rep.Conc. | URIs length for Semantic Kalevala took 4.848932266235352s
Interoperability | New vocabularies check for Semantic Kalevala took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.2553551197052002s
Accuracy | Check Functional Property for Semantic Kalevala took 0.19027924537658691s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.16105246543884277s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.938199520111084s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.29833507537841797s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.4230241775512695s
Consistency | Disjoint class check for Semantic Kalevala took 0.1521306037902832s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7857115268707275s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.4215950965881348s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.4533872604370117s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.6387910842895508s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9402072429656982s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.26584315299987793s
Security | Sign check for Semantic Kalevala took 0.16123056411743164s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2301.3315165042877s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.7884557247161865s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.9073486328125e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.2636184692382812e-05s
INFO | --- Analysis for Semantic-Kalevala took 2363.957567214966s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9727859497070312s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0006546974182128906s
Extra | Recovery of all triples for Smithsonian American Art Museum took 274.0664930343628s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.236355781555176s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5901367664337158s
Interoperability | New terms check for Smithsonian American Art Museum took 3.0830211639404297s
Versatility | Languages check for Smithsonian American Art Museum took 30.710415601730347s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.6148061752319336s
Security | Check HTTPS for Smithsonian American Art Museum took 0.3633387088775635s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.7251942157745361s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.7240700721740723s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6388614177703857s
License | MR license check for Smithsonian American Art Museum took 0.6308777332305908s
License | HR license check for Smithsonian American Art Museum took 16.776061296463013s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5912976264953613s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5922155380249023s
Understandability | URI regex check for Smithsonian American Art Museum took 1.2402150630950928s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6071035861968994s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6746418476104736s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.615908145904541s
Performance | Throughput check for Smithsonian American Art Museum took 11.895539283752441s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 8.511543273925781e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6092977523803711s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.6001498699188232s
Interlinking | skos check for Smithsonian American Art Museum took 0.6010799407958984s
Interlinking | skos check for Smithsonian American Art Museum took 0.5861186981201172s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5905871391296387s
Currency | Creation date check for Smithsonian American Art Museum took 1.247035026550293s
Currency | Modification date check for Smithsonian American Art Museum took 1.2573785781860352s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 103.54075980186462s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5902972221374512s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 20.594282627105713s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5109212398529053s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.311921834945679s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5950300693511963s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.071663856506348s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 101.90040993690491s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.6397063732147217s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 6.034708499908447s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 3.0136849880218506s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6377902030944824s
Security | Sign check for Smithsonian American Art Museum took 0.6094896793365479s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.405523300170898s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.4251742362976074s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.021491289138793945s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.8596649169921875e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.1457672119140625e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.1205673217773438e-05s
INFO | --- Analysis for Smithsonian took 702.0434794425964s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.2292928695678711s
Availability | VoID file availability check for Zeri Photo Archive took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.29303669929504395s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.239776611328125e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.0013580322265625e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 6.344147682189941s
Availability | SPARQL endpoint availability check for Archives Hub took 21.658609628677368s
Availability | VoID file availability check for Archives Hub took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.28496313095092773s
Reputation | Calculation of the PageRank for Archives Hub took 0.021519899368286133s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.1920928955078125e-05s
Believability | Calculation of trust value for Archives Hub took 1.3113021850585938e-05s
INFO | --- Analysis for Archives-Hub took 55.013468980789185s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.6901576519012451s
Availability | VoID file availability check for Yale centre of British Art took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.3106424808502197s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.1920928955078125e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.239776611328125e-05s
INFO | --- Analysis for Yale took 5.026590347290039s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 263.96302676200867s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.3110523223876953s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.021252155303955078s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.000990152359008789s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.6450881958007812e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.3589859008789062e-05s
INFO | --- Analysis for ADL took 539.0175378322601s
Availability | SPARQL endpoint availability check for MusicKG took 0.6678433418273926s
Availability | VoID file availability check for MusicKG took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for MusicKG took 0.33193039894104004s
Reputation | Calculation of the PageRank for MusicKG took 0.02147841453552246s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0010290145874023438s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.2636184692382812e-05s
Believability | Calculation of trust value for MusicKG took 1.2636184692382812e-05s
INFO | --- Analysis for MusicKG took 4.583683967590332s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.8052170276641846s
Availability | VoID file availability check for CIDOC-CRM took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.3059360980987549s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.021904706954956055s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 3.457069396972656e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.430511474609375e-05s
INFO | --- Analysis for CIDOC-CRM took 4.526007890701294s
Availability | SPARQL endpoint availability check for Mondis took 262.2033519744873s
Availability | VoID file availability check for Mondis took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Mondis took 0.300520658493042s
Reputation | Calculation of the PageRank for Mondis took 0.02226400375366211s
Interlinking | Calculation of Degree of Connection for Mondis took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0008218288421630859s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.52587890625e-05s
Believability | Calculation of trust value for Mondis took 1.2874603271484375e-05s
INFO | --- Analysis for Mondis took 265.50538873672485s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.358246326446533s
Availability | VoID file availability check for DigitalNZ took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.3424386978149414s
Reputation | Calculation of the PageRank for DigitalNZ took 0.022444725036621094s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0008292198181152344s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.33514404296875e-05s
Believability | Calculation of trust value for DigitalNZ took 1.1920928955078125e-05s
INFO | --- Analysis for DigitalNZ took 7.553878307342529s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.1798386573791504s
Availability | VoID file availability check for Fondazione Zeri took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.3096470832824707s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.1205673217773438e-05s
Believability | Calculation of trust value for Fondazione Zeri took 7.62939453125e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.605022430419922s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.157912015914917s
Availability | VoID file availability check for Digital Public Library of America took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.3322265148162842s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.022580623626708984s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.3113021850585938e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.33514404296875e-05s
INFO | --- Analysis for Library-of-America took 4.259741544723511s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.4885685443878174s
Availability | VoID file availability check for Auckland Museum took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.2979555130004883s
Reputation | Calculation of the PageRank for Auckland Museum took 0.02221965789794922s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.1444091796875e-05s
Believability | Calculation of trust value for Auckland Museum took 1.1444091796875e-05s
INFO | --- Analysis for Auckland-Museum took 6.746917009353638s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.6162939071655273s
Availability | VoID file availability check for National Library of Spain took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2935061454772949s
Reputation | Calculation of the PageRank for National Library of Spain took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.0967254638671875e-05s
Believability | Calculation of trust value for National Library of Spain took 1.1205673217773438e-05s
INFO | --- Analysis for BNE took 4.8932623863220215s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.3004424571990967s
Availability | VoID file availability check for National Library of Korea took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.27429962158203125s
Reputation | Calculation of the PageRank for National Library of Korea took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.1205673217773438e-05s
Believability | Calculation of trust value for National Library of Korea took 6.9141387939453125e-06s
INFO | --- Analysis for Korea-Library took 4.478814125061035s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.5566132068634033s
Availability | VoID file availability check for The State Russian Museum took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.287886381149292s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.1205673217773438e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.5497207641601562e-05s
INFO | --- Analysis for Russian-Museum took 4.853951692581177s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.7357439994812012s
Availability | VoID file availability check for National Library of Scotland took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.2886991500854492s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.02111053466796875s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.33514404296875e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.2636184692382812e-05s
INFO | --- Analysis for National-Library-of-Scotland took 7.383350133895874s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.8767457008361816s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.32824039459228516s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.2159347534179688e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.5497207641601562e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 4.413136720657349s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.22231626510620117s
Availability | VoID file availability check for OntoComedySources took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.31544017791748047s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.1920928955078125e-05s
Believability | Calculation of trust value for OntoComedySources took 8.106231689453125e-06s
INFO | --- Analysis for OntoComedySources took 4.3305745124816895s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.20091676712036133s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.28976917266845703s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.021331071853637695s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.239776611328125e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.2159347534179688e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 4.678504467010498s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.13432693481445312s
Availability | VoID file availability check for SaintGall Ontology took 0.00035691261291503906s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.33799099922180176s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.022172927856445312s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.1682510375976562e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.1444091796875e-05s
INFO | --- Analysis for SaintGall-Ontology took 3.4354777336120605s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.6544158458709717s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.2945864200592041s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.022574424743652344s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.239776611328125e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.096385478973389s
Availability | SPARQL endpoint availability check for ICON took 0.3488597869873047s
Availability | VoID file availability check for ICON took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for ICON took 0.3110368251800537s
Reputation | Calculation of the PageRank for ICON took 0.02151966094970703s
Interlinking | Calculation of Degree of Connection for ICON took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for ICON took 1.049041748046875e-05s
Believability | Calculation of trust value for ICON took 7.3909759521484375e-06s
INFO | --- Analysis for ICON took 4.586147785186768s
Availability | SPARQL endpoint availability check for Polifonia took 0.25029587745666504s
Availability | VoID file availability check for Polifonia took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Polifonia took 0.29523777961730957s
Reputation | Calculation of the PageRank for Polifonia took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.1444091796875e-05s
Believability | Calculation of trust value for Polifonia took 1.33514404296875e-05s
INFO | --- Analysis for Polifonia took 4.612974643707275s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.23630976676940918s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.3065359592437744s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.33514404296875e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.1920928955078125e-05s
INFO | --- Analysis for Atlas-of-Paths took 4.290936708450317s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.203751802444458s
Availability | VoID file availability check for Music Note Ontology took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.30203723907470703s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for Music Note Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Music-Note-Ontology took 8.686864852905273s
Availability | SPARQL endpoint availability check for HaMSE took 0.1898665428161621s
Availability | VoID file availability check for HaMSE took 0.0012085437774658203s
Completeness | Calculation of interlinking completeness for HaMSE took 0.28806638717651367s
Reputation | Calculation of the PageRank for HaMSE took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.0251998901367188e-05s
Believability | Calculation of trust value for HaMSE took 1.2159347534179688e-05s
INFO | --- Analysis for HaMSE took 5.347848653793335s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.11806344985961914s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0013959407806396484s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.30156421661376953s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.022306442260742188s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1682510375976562e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.3828277587890625e-05s
INFO | --- Analysis for FOod took 5.153554677963257s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.6986281871795654s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.29376220703125s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.02095770835876465s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.2874603271484375e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.049041748046875e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.5217125415802s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.48052978515625s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.281278133392334s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.1205673217773438e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 1.049041748046875e-05s
INFO | --- Analysis for ARIADNE took 5.95601749420166s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 7.939338684082031e-05s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.3113861083984375s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.022950172424316406s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 3.4332275390625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.6927719116210938e-05s
INFO | --- Analysis for rijksmuseum took 3.2815396785736084s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.35472559928894043s
Availability | VoID file availability check for Odeuropa Ontology took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.28986525535583496s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.6689300537109375e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.1444091796875e-05s
INFO | --- Analysis for Odeuropa took 3.6075515747070312s

--- Total time for analysis:497825.9939625263s ---
--- Total time for analysis:138.28499832292397 hours ---